[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fj57XmFktHYVmmROwWefLyhzI37XYUSvR52cEdLIfVT4":3,"$f445NT0n4jwvEtfYZLpxKLXRUzcb7ydFd8YZjHqKV1Kk":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"vercel-changelog","Vercel API","vercel","openapi-json","rest","https:\u002F\u002Fopenapi.vercel.sh\u002F",{"id":13,"contentHash":14,"fetchedAt":15},"01KX745J13FV2NGPS9HFYH8Y2C","4e5e4065d8e465e0f7e81a4c8e2fa06f9561f8dd0ac9390e552de673e6755ce8","2026-07-10T23:00:25.759Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KX7NATCA5TR48TJ41E6XYR36","c78b02d1ab19b60466fe7e8f9e6ce0288b134023e369730d47bbf912f9a77b75","2026-07-11T04:00:24.499Z",null,{"alerts":22},[23,30,36,43,50,57,64,71,79,87,94,101,108,115,122,129,136,143,150,157,164,171,178,185,192,199,206,213,220,227,234,241,248,255,262,269,276,283,290,297,304,311,318,325,332,339,346,353,360,367],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KX7NAZEDT50APJEEF1GJGBMY","Additive","Add firewall OAuth scopes to Vercel API","The Vercel API now includes two new OAuth scopes: `read-write:firewall` and `read:firewall`. These scopes are added to multiple endpoints and can be requested by applications that need firewall configuration management capabilities. This is purely additive and does not affect existing integrations.","2026-07-11T04:00:30.669Z","2026-07-11-add-firewall-oauth-scopes-to-vercel-api",{"id":31,"severity":25,"title":32,"summary":33,"contentHash":14,"detectedAt":34,"slug":35},"01KX745QSZ63RA53TF3MA813W8","Add creator field to domain and project response objects","The Vercel API now includes a new optional `creator` field in domain and project response schemas. This field captures who created the resource (user, app, integration, or system), with optional delegation details for OAuth-delegated actions. This is purely additive and does not break existing integrations.","2026-07-10T23:00:33.215Z","2026-07-10-add-creator-field-to-domain-and-project-response-objects",{"id":37,"severity":25,"title":38,"summary":39,"contentHash":40,"detectedAt":41,"slug":42},"01KX6XA292C6NANPNFANKE4Z4D","Add passport-access-granted event type and external principal metadata","The Vercel API now supports a new `passport-access-granted` event type and adds support for external principals (non-system identities) with `id`, `name`, and `email` fields in event metadata. Additionally, a new event payload structure is introduced for passport access events containing environment, host, connector, and session details. These are purely additive changes that do not affect existing integrations.","57023e35806de819a81ba2192256bb7e3681ebfcb2c90433ae8cac74e0c1d313","2026-07-10T21:00:34.978Z","2026-07-10-add-passport-access-granted-event-type-and-external",{"id":44,"severity":25,"title":45,"summary":46,"contentHash":47,"detectedAt":48,"slug":49},"01KX68Q2V8QTCJ07T7WQ28QMQF","Add organization-delete event type","The Vercel API now includes a new `organization-delete` event type in audit log event enumerations. This is a new optional event value that applications can now receive and handle in audit log webhooks and event streams.","f1f2bcd2acd3757215e44c63c1e55bea8368a770638ead9732a56e1063e2ebcc","2026-07-10T15:00:41.448Z","2026-07-10-add-organization-delete-event-type",{"id":51,"severity":25,"title":52,"summary":53,"contentHash":54,"detectedAt":55,"slug":56},"01KX5M3NH9HQMAWAGV2DWHM4TF","Add aiGatewayBudget ACL action field","A new optional field **aiGatewayBudget** has been added to multiple ACL-related request\u002Fresponse schemas in the Vercel API. This field is an array of `ACLAction` objects, following the same structure as the existing `aiGatewayCredits` field. Since it is additive and does not modify existing fields or remove functionality, clients can safely ignore it without impact.","67946afc4cda31f343300c7bb4248247a29adbf48e6885441b3b08a9213b2820","2026-07-10T09:00:33.705Z","2026-07-10-add-aigatewaybudget-acl-action-field",{"id":58,"severity":25,"title":59,"summary":60,"contentHash":61,"detectedAt":62,"slug":63},"01KX4HRYM71BCS3X7G4JRA386S","Add tanstack-start-lovable framework support","The Vercel API now includes `tanstack-start-lovable` as a supported framework option in framework enumeration fields. This is an additive change allowing deployments to specify this new framework type without breaking existing integrations.","775da11714aa46f188738b9e7ece88a32ca6d77601e41e0e446afcf5004586cb","2026-07-09T23:00:30.983Z","2026-07-09-add-tanstack-start-lovable-framework-support",{"id":65,"severity":25,"title":66,"summary":67,"contentHash":68,"detectedAt":69,"slug":70},"01KX4AX90YF7N9VKNGQJTVERQ1","Add Passport publicPathRules and enforcementScope fields","Three new optional fields added to the Vercel API: **publicPathRules** (array of path matching rules) in the passport configuration, and **enforcementScope** (with values \"all\" or \"preview\") in two different security policy contexts. These are backwards-compatible additions that enable new functionality without affecting existing integrations.","b51ae7a9d71e82544b448e756431d0b1be97113f25abd45d18faa5c788fc0182","2026-07-09T21:00:32.670Z","2026-07-09-add-passport-publicpathrules-and-enforcementscope-fields",{"id":72,"severity":73,"title":74,"summary":75,"contentHash":76,"detectedAt":77,"slug":78},"01KX441GJ5JWHX6H8A53ZYKFMN","Informational","Removed empty 402 error response descriptions from OpenAPI","The OpenAPI specification removed two instances of HTTP 402 error responses that had empty descriptions from unspecified endpoints. These changes are documentation\u002Fschema cleanup with no impact on actual API behaviour or functionality.","31b468067f14f2a8302ddac408bebc8ff5e61dbfe7dbd664dad4e1f9b23d16e9","2026-07-09T19:00:31.429Z","2026-07-09-removed-empty-402-error-response-descriptions-from-openapi",{"id":80,"severity":81,"title":82,"summary":83,"contentHash":84,"detectedAt":85,"slug":86},"01KX40KVKV7V8DP1MVSKV32NGQ","Breaking","Remove dheCipherSuite field and 409\u002F500 response codes from API spec","Two distinct breaking changes are present: **1)** The `dheCipherSuite` response field (type `string`) has been removed from multiple log\u002Fevent response schemas — it also appears in `required` arrays, meaning clients that rely on its presence will break. **2)** The `409` and `500` response status codes have been removed from one endpoint's documented responses, which may affect error-handling logic in clients that branch on those codes.","b1b6b05001bf70e9e3660558cb738e50d497e1bd57ed526829ae846b79b6dca4","2026-07-09T18:00:38.267Z","2026-07-09-remove-dheciphersuite-field-and-409-500-response-codes-from",{"id":88,"severity":25,"title":89,"summary":90,"contentHash":91,"detectedAt":92,"slug":93},"01KX3PA4GYD6NXRN2HSTZY22W2","Add user-emu-account-deleted webhook event type","The Vercel API now includes a new webhook event type `user-emu-account-deleted` in the list of supported events. This is a purely additive change that enables integrations to receive notifications when enterprise managed user accounts are deleted.","63e1197b17dedc53bfc176d51108fde307b1809f7a61e6fad3ff44f81863d5aa","2026-07-09T15:00:33.950Z","2026-07-09-add-user-emu-account-deleted-webhook-event-type",{"id":95,"severity":25,"title":96,"summary":97,"contentHash":98,"detectedAt":99,"slug":100},"01KX3JWHMXE83XJXPDG0V6BPXB","Add alias, aliasError, aliasWarning fields to deployment event response","Three new response fields — **`alias`**, **`aliasError`**, and **`aliasWarning`** — are added to deployment event objects in two response schemas (likely covering two related list\u002Fget endpoints). `alias` is a string array; `aliasError` and `aliasWarning` are nullable objects with `code` and `message` (required), plus optional `link` and `action` on `aliasWarning`. Although listed as `required` in the schema, these are net-new fields added to the response, so existing clients that ignore unknown fields are unaffected — no existing fields were removed or changed.","d7fd5c33fce46dc3c8be7e946c31ca0b5496087186e5daae906980a1fa705ef8","2026-07-09T14:00:42.909Z","2026-07-09-add-alias-aliaserror-aliaswarning-fields-to-deployment",{"id":102,"severity":25,"title":103,"summary":104,"contentHash":105,"detectedAt":106,"slug":107},"01KX3FENH6ENJPSY3NPKMQJ7C0","Add mfe_group_ids array field to environment schemas","A new optional `mfe_group_ids` array field (containing string items) has been added to environment response schemas across multiple API endpoints. This is a purely additive change that allows clients to optionally consume the new field without breaking existing integrations.","a624108980c1530ddde3ed1a290a0ca5feecdb79ba9b166b8720610a9b0d0af8","2026-07-09T13:00:42.406Z","2026-07-09-add-mfe-group-ids-array-field-to-environment-schemas",{"id":109,"severity":25,"title":110,"summary":111,"contentHash":112,"detectedAt":113,"slug":114},"01KX31QEXD3QF34D1HHBF6R538","Add new log event types to deployment logs","The Vercel API now includes additional log event type schemas in deployment logs, supporting new event types like `command`, `delimiter`, `deployment-state`, `edge-function-invocation`, `exit`, `fatal`, `metric`, `middleware`, `middleware-invocation`, `report`, `stderr`, and `stdout`. These new schemas add support for structured payload data including proxy metrics and edge function details, while maintaining backward compatibility by keeping the previously supported event type available.","9b6358ebe82fdeebf832fbee4acea4207dce56925c16b5e5db21d5ba6e79864f","2026-07-09T09:00:50.477Z","2026-07-09-add-new-log-event-types-to-deployment-logs",{"id":116,"severity":25,"title":117,"summary":118,"contentHash":119,"detectedAt":120,"slug":121},"01KX22THGF2KYA1ER7F6SD73HF","Add strictPasswordProtectionSettings to API schema","A new `strictPasswordProtectionSettings` object property has been added to the API schema, allowing project owners to require Owner role for password protection changes. This is an additive change that includes the new field in team settings responses and introduces a corresponding audit log event type (`strict-password-protection-settings`).","61be999d4c584ba579e8624baab7837be15a305a0a4d5085d1e7a99bf56dd872","2026-07-09T00:00:45.583Z","2026-07-09-add-strictpasswordprotectionsettings-to-api-schema",{"id":123,"severity":25,"title":124,"summary":125,"contentHash":126,"detectedAt":127,"slug":128},"01KX1VZ3WVJEG3JYH5KNYV59HR","Add organization-slug-update event type and payload schema","The Vercel API adds a new `organization-slug-update` event type to three locations in the OpenAPI specification, along with a new payload schema containing `organizationId` and `slug` fields. This is purely additive and enables customers to subscribe to organization slug update events without affecting existing integrations.","f74aec5bbb07993a310a3236500260f53abd0a05e054b3ff4c6f999d3210f5a4","2026-07-08T22:00:55.451Z","2026-07-08-add-organization-slug-update-event-type-and-payload-schema",{"id":130,"severity":25,"title":131,"summary":132,"contentHash":133,"detectedAt":134,"slug":135},"01KX1AS3S924GTG0GBQX6MTT2R","Add organization-create event type support","The Vercel API now supports a new `organization-create` event type in webhooks. This includes a new event payload schema with fields `rootTeamId`, `slug`, and `name` alongside the existing `organizationId`. The change is backwards-compatible as it only adds new options to existing event type enumerations and introduces a new optional event payload variant.","3ff660568354d6e0a06d2b58d7787ccf464315c1ba3f8b2fa0bdf4dffe2615f2","2026-07-08T17:00:32.937Z","2026-07-08-add-organization-create-event-type-support",{"id":137,"severity":25,"title":138,"summary":139,"contentHash":140,"detectedAt":141,"slug":142},"01KX10FNTPC532KVP33M0380T9","Add headers source type and transforms\u002Frulesets fields","The diff adds **`headers`** as a new enum option to source type fields (alongside existing `header`, `cookie`, `environment`, etc.), introduces a new **`transforms`** array field supporting header manipulation operations, and adds a comprehensive **`rulesets`** field with support for advanced rule conditions and actions including rate limiting, redirects, and logging. These are all purely additive schema changes that extend existing security\u002Frouting configurations without removing or breaking existing functionality.","76d57ccace2f1f3c12625c2c13728cb090d4a993aea0bd7d989856a1f8710c81","2026-07-08T14:00:37.974Z","2026-07-08-add-headers-source-type-and-transforms-rulesets-fields",{"id":144,"severity":25,"title":145,"summary":146,"contentHash":147,"detectedAt":148,"slug":149},"01KX01JR4JTJXH5Z6P85GY1GK4","Add omitScriptNonce boolean field to security options","A new optional boolean field `omitScriptNonce` has been added to security configuration objects in the Vercel API. This allows users to control script nonce behavior when configuring security headers, and does not break existing integrations as the field is optional.","c609930940eff278a53b83b5fbb1a2867cbf599c74ebc3d9536ee7463bb29a62","2026-07-08T05:00:32.786Z","2026-07-08-add-omitscriptnonce-boolean-field-to-security-options",{"id":151,"severity":25,"title":152,"summary":153,"contentHash":154,"detectedAt":155,"slug":156},"01KWZKV7TJ056442Y4GTMJ5ZT7","Add AI Gateway guardrails and moderation fields to API","The Vercel API adds support for AI Gateway guardrails via new `aiGatewayGuardrails` ACL action fields, moderation fields (`moderationApplied`, `piiRedactionApplied`) in response schemas, and new auth scopes (`read-write:ai-gateway-guardrails`, `read:ai-gateway-guardrails`). A new webhook event type `ai-gateway-guardrails-updated` is also introduced. These are purely additive changes with no impact on existing integrations.","c517ed44227b14fe38de7f3f57ff2b7cbb82f03618d4f35362826f193db807d4","2026-07-08T01:00:30.930Z","2026-07-08-add-ai-gateway-guardrails-and-moderation-fields-to-api",{"id":158,"severity":25,"title":159,"summary":160,"contentHash":161,"detectedAt":162,"slug":163},"01KWYVTEJ2779062TTTGQV06ZR","Add DELETE artifacts endpoint and new auth\u002Fevent scopes","This change adds a new **DELETE \u002Fv1\u002Fartifacts** endpoint to clear all remote cache artifacts for a team, new OAuth permission scopes (`manage:speed-insights`, `manage:web-analytics`, `read:speed-insights`, `read:web-analytics`), and a new webhook event type `team-remote-caching-purge`. All additions are purely new without breaking existing API contracts.","7d084a838566df05d6ac1b6174d814b5fe10a8c536b3fd834deded0f2ecb48ec","2026-07-07T18:00:39.234Z","2026-07-07-add-delete-artifacts-endpoint-and-new-auth-event-scopes",{"id":165,"severity":25,"title":166,"summary":167,"contentHash":168,"detectedAt":169,"slug":170},"01KWYRCC12SH1V0WJRGKPH0TP2","Add OIDC token-exchange grant and audit log fields","The Vercel API now supports the `urn:ietf:params:oauth:grant-type:token-exchange` grant type for OAuth flows and adds three new optional response fields to audit logs: `issuerUrl`, `policyId`, and `oidcSubject`. These changes enable OIDC-authenticated token exchange workflows and provide enhanced audit trail information for authentication flows.","37c7379427a20242baad14aa2e431035a8732bc62c39c905f0a6b01d083052fd","2026-07-07T17:00:32.162Z","2026-07-07-add-oidc-token-exchange-grant-and-audit-log-fields",{"id":172,"severity":25,"title":173,"summary":174,"contentHash":175,"detectedAt":176,"slug":177},"01KWYMYMD42ZW9V354SEFX4YTF","Add \"attestation\" enum value to manifest kind field","The `kind` field now accepts a new enum value `\"attestation\"` in addition to `\"index\"` and `\"manifest\"`. This is an additive change that expands what types of container image manifests can be represented; existing integrations using the previous enum values will continue to work, but may now encounter the new value in responses.","df94ed6853c59420aefde7d436a42ebfece48be62919d9fe80a1739c200a155a","2026-07-07T16:00:36.260Z","2026-07-07-add-attestation-enum-value-to-manifest-kind-field",{"id":179,"severity":25,"title":180,"summary":181,"contentHash":182,"detectedAt":183,"slug":184},"01KWXWXCZ984SGB8YECR99F590","Add cacheReason field and durationMs to Vercel API responses","Two new optional response fields have been added to the Vercel API: **`cacheReason`** (type: string) has been added to multiple response schemas across different endpoints (appearing in 6 locations), and **`durationMs`** (type: number) has been added to command execution data. These are purely additive changes that expand response information without affecting existing integrations.","29bf653664d9b33309a77aa66c53a14a0657b087f15387c8aacf0917eee07b30","2026-07-07T09:00:30.057Z","2026-07-07-add-cachereason-field-and-durationms-to-vercel-api-responses",{"id":186,"severity":25,"title":187,"summary":188,"contentHash":189,"detectedAt":190,"slug":191},"01KWX1ESJC0P2A359FB7P4ATGB","Add blobs.isDefaultApp field and teamThrottled field to project schemas","This change adds two new optional response fields to project schemas: `blobs.isDefaultApp` (a boolean marking the default team-level Vercel-managed blob project) and `teamThrottled` (a boolean synced from team billing status indicating team-wide throttling). Both are new optional fields appearing in multiple project response objects across the API, along with refinement of the `throttled` field description to clarify it applies to per-project rather than team-level throttling. A new `read-write:team-members` authorization scope is also added to several token scopes. These changes are purely additive and will not break existing clients.","bed5709e7669f66bffd211e33d2598fec6eeb27f2feccf7f4b71bd35770e4c08","2026-07-07T01:00:39.884Z","2026-07-07-add-blobs-isdefaultapp-field-and-teamthrottled-field-to",{"id":193,"severity":25,"title":194,"summary":195,"contentHash":196,"detectedAt":197,"slug":198},"01KWVR8KMNRG727H6K3FXER52V","Add alert-investigation-project-allowlist-updated event type","A new event type `alert-investigation-project-allowlist-updated` has been added to the Vercel API webhook\u002Fevent system, along with a new event payload schema containing `previousProjectCount` and `nextProjectCount` fields. This is a purely additive change that enables clients to subscribe to and handle allowlist update events without breaking existing integrations.","c374dcc36f40294fc191a861336462705ba5ae8f1f50f298f0b4e47024133d54","2026-07-06T13:00:45.589Z","2026-07-06-add-alert-investigation-project-allowlist-updated-event-type",{"id":200,"severity":25,"title":201,"summary":202,"contentHash":203,"detectedAt":204,"slug":205},"01KWKKAHPYRWF7TVTNFWGSZB8A","Add expiresAt field to sandbox response","A new optional response field `expiresAt` has been added to the sandbox schema, indicating when the currently running sandbox will time out. This is a purely additive change that does not affect existing integrations.","5fa7e2b359f7629fa0dd13b957bf574cc60453dfdd87bf95c148c7955a4a46a9","2026-07-03T09:00:30.814Z","2026-07-03-add-expiresat-field-to-sandbox-response",{"id":207,"severity":25,"title":208,"summary":209,"contentHash":210,"detectedAt":211,"slug":212},"01KWHRYY758X5P76ZZD8P40MKF","Add providerAttemptSafetyIdentifier fields and read:remote-cache scope","Two new optional response fields (`providerAttemptSafetyIdentifier` and `providerAttemptDevSafetyIdentifier`) have been added to provider attempt objects in multiple endpoints, and a new optional OAuth scope (`read:remote-cache`) has been introduced. These additions do not break existing clients and are purely additive.","018ef848ed5d22d141a532d815fa955033e4ebbe219c612ad3e0907497e22fb8","2026-07-02T16:00:32.997Z","2026-07-02-add-providerattemptsafetyidentifier-fields-and-read-remote",{"id":214,"severity":25,"title":215,"summary":216,"contentHash":217,"detectedAt":218,"slug":219},"01KWHB7E0FFET2XAN5C6QGBBQT","Add vcr field to user blocks object in user details","Added a new optional `vcr` field to the user blocks response object, containing blockage information for VCR features with properties like `blockReason`, `blockedFrom`, `blockedUntil`, and `updatedAt`. This is a purely additive change that does not affect existing integrations.","7e06fad0d63525ec3e521980c51a2fada7248d1c6bc17f1adf3184be36ed5193","2026-07-02T12:00:31.247Z","2026-07-02-add-vcr-field-to-user-blocks-object-in-user-details",{"id":221,"severity":25,"title":222,"summary":223,"contentHash":224,"detectedAt":225,"slug":226},"01KWH4BP0D920GQ8QB2SFH36MY","Add VCR get repository tag endpoint","A new endpoint `GET \u002Fv1\u002Fvcr\u002Frepository\u002F{idOrName}\u002Ftags\u002F{tag}` has been added to fetch a single tag from a Vercel Container Registry repository along with image metadata and VHS-readiness status. A new `VcrTag` schema was introduced to support this endpoint's response. This is a purely additive change that extends the VCR API without modifying existing behavior.","f5dc33172792a2839d733ec350d103183e2d4674d0b9763cf238c9aa93e50f40","2026-07-02T10:00:30.477Z","2026-07-02-add-vcr-get-repository-tag-endpoint",{"id":228,"severity":25,"title":229,"summary":230,"contentHash":231,"detectedAt":232,"slug":233},"01KWF6J8QF19GCE3JVV473WSBP","Add DOMAIN_OWNER_DELETION_REQUEST suspension reason","A new enum value `DOMAIN_OWNER_DELETION_REQUEST` has been added to the `reason` field in suspension-related response schemas. This is an additive change that expands the set of documented suspension reasons without breaking existing integrations.","7d9f5a389d24f4893b349e09c4d176765004a15731b0723a9d6ded6e6782c7eb","2026-07-01T16:00:34.543Z","2026-07-01-add-domain-owner-deletion-request-suspension-reason",{"id":235,"severity":73,"title":236,"summary":237,"contentHash":238,"detectedAt":239,"slug":240},"01KWF34A3XXQWV6R0VK5GEPQT6","Update environment variable creation error descriptions","Error response descriptions for environment variable creation endpoints were updated: the 403 response removed text about production variable permission requirements, and the 409 response description was cleared. These are documentation-only changes to error messaging that do not affect API behavior or client integrations.","3734154337e470acba79931f22dbd593cad772b3b62320cb99248cda9505f189","2026-07-01T15:00:31.485Z","2026-07-01-update-environment-variable-creation-error-descriptions",{"id":242,"severity":25,"title":243,"summary":244,"contentHash":245,"detectedAt":246,"slug":247},"01KWEEH2SGTQB2C5H8JJX7KYS8","Add attributionTarget and attributionEventName fields","Two new optional response fields, `attributionTarget` and `attributionEventName`, have been added to analytics\u002Flogs endpoints. These fields are purely additive and do not affect existing integrations.","b94a0e9a535c8d5677fe20a143b5e55daf8f3dfab26dd28321bd66cd300e24d7","2026-07-01T09:00:29.872Z","2026-07-01-add-attributiontarget-and-attributioneventname-fields",{"id":249,"severity":25,"title":250,"summary":251,"contentHash":252,"detectedAt":253,"slug":254},"01KWDPG0RYZW05GZHDASF1QGP9","Add \"list\" operator for filtering in Vercel API","The Vercel API adds a new `\"list\"` operator (type: string) to filter query parameters across multiple endpoints. This is purely additive — the new operator appears as an optional field in filter objects and an allowed enum value, enabling clients to perform new filtering operations without breaking existing code.","6ff51a1093060f07c49acc6c22bf69506d54ed4443b6d1acb24af39141aa38d0","2026-07-01T02:00:29.214Z","2026-07-01-add-list-operator-for-filtering-in-vercel-api",{"id":256,"severity":25,"title":257,"summary":258,"contentHash":259,"detectedAt":260,"slug":261},"01KWDC6FC742SRXSTWE09FGFAF","Add build-timeout-failure to buildMachineElasticReason enum and new reason field","The Vercel API adds a new enum value `build-timeout-failure` to the `buildMachineElasticReason` field across multiple endpoints and response schemas. Additionally, a new optional `reason` field is added to describe why build machines were upgraded or downgraded. Both changes are purely additive and cannot break existing integrations.","434af89d187585101eae63c3104eb5cee77499800839b5b265c86498779f4b88","2026-06-30T23:00:30.727Z","2026-06-30-add-build-timeout-failure-to-buildmachineelasticreason-enum",{"id":263,"severity":25,"title":264,"summary":265,"contentHash":266,"detectedAt":267,"slug":268},"01KWD5AVT2Y0EP1JZ20ZHHQ5Q8","Add buildMachineElasticReason field and team identifiers","A new optional response field `buildMachineElasticReason` (enum string) has been added to multiple build\u002Fdeployment response objects across the API, providing insight into why a build machine type was selected. Additionally, two new required fields `teamId` and `slug` have been added to the `managedTeams` object structure. These are purely additive changes that expand the API's response surface without breaking existing clients.","202be92de9517e016c3e9db04536a5568f222ca615ec3627ec976832f2064cb7","2026-06-30T21:00:34.498Z","2026-06-30-add-buildmachineelasticreason-field-and-team-identifiers",{"id":270,"severity":25,"title":271,"summary":272,"contentHash":273,"detectedAt":274,"slug":275},"01KWCM5F6ZYNRR6CRTG5FJSA0F","Add security-list audit event types","Three new audit event types have been added: `security-list-created`, `security-list-deleted`, and `security-list-updated`. These are additive extensions to the audit event enumeration that allow tracking of security list management operations.","20b2306fcbaea200accc7cb4cf5204e0aeb6e70cc33fd4e54584a438d1f50888","2026-06-30T16:00:31.967Z","2026-06-30-add-security-list-audit-event-types",{"id":277,"severity":25,"title":278,"summary":279,"contentHash":280,"detectedAt":281,"slug":282},"01KWBZJ9XV32G3C13Q0FXDQVBF","Add VCR (Vercel Container Registry) API and image sandbox support","The Vercel API introduces new container registry management endpoints under `\u002Fv1\u002Fvcr\u002F` and related schemas for managing repositories, images, and image metadata. Additionally, an `image` field is added to the sandbox configuration schema. These are purely additive changes that do not break existing integrations.","3eaedea15f212ca86bb213d80aacfe63ea82b0f97f10c0c63598f5fe6e0b00cb","2026-06-30T10:00:32.443Z","2026-06-30-add-vcr-vercel-container-registry-api-and-image-sandbox",{"id":284,"severity":25,"title":285,"summary":286,"contentHash":287,"detectedAt":288,"slug":289},"01KWBECWRQS5HWPR3RPKK159EV","Add AI Gateway model allowlist webhook events","Two new webhook event types have been added: `ai-gateway-model-allowlist-toggled` and `ai-gateway-model-allowlist-models-updated`. These represent new AI Gateway model allowlist events with their own payload schemas (toggled event includes a boolean `enabled` field; models-updated includes `added` and `removed` string array fields). This is purely additive and does not affect existing integrations.","fc581d823b56a713698a659af361dc0efff79f45d75b5e0b3d5f27d9a7832193","2026-06-30T05:00:29.335Z","2026-06-30-add-ai-gateway-model-allowlist-webhook-events",{"id":291,"severity":25,"title":292,"summary":293,"contentHash":294,"detectedAt":295,"slug":296},"01KWAX80A3EPFYS7VP4RDD2M5R","Expand deployment response schema with new fields and enums","The deployment object response schema gains several new fields (`checksConclusion`, `checksState`, `connectBuildsEnabled`, `connectConfigurationId`, `deletedAt`, `monorepoManager`, `oidcTokenClaims`, `previewCommentsEnabled`, `readyAt`, `readySubstate`) and adds enum constraints to existing fields (`plan`, `readyState`, `type`). Additionally, the `alias` field is now required. All changes are backward-compatible additions; existing clients receive new fields in responses but can ignore them if not needed.","e347bc2ae06fd53349cf6dd588368a65927dff4268164e97f1027fa57084e717","2026-06-30T00:00:43.331Z","2026-06-30-expand-deployment-response-schema-with-new-fields-and-enums",{"id":298,"severity":81,"title":299,"summary":300,"contentHash":301,"detectedAt":302,"slug":303},"01KWASSYHXGWTGSRVFKW5P21KJ","Project ID path param type narrowed from oneOf[string|boolean] to string","The schema for the `idOrName` path parameter (project identifier) was changed from `oneOf: [string, boolean]` to `type: string`. Any client passing a boolean value for this parameter will now be considered invalid per the spec. In practice, a boolean project identifier was likely never a valid use case, but generated clients or strict validators that relied on the `boolean` variant being allowed may break.","138fb318ff248e76720d3f0d1cc7e04449046675295fb80f4fb304e61cd4608a","2026-06-29T23:00:37.053Z","2026-06-29-project-id-path-param-type-narrowed-from-oneof-string",{"id":305,"severity":81,"title":306,"summary":307,"contentHash":308,"detectedAt":309,"slug":310},"01KWAPC0PKTWGKHZFH77FQGVSF","Two usage record field keys renamed in response schema","Two fields in a response object have been renamed: **`workflowStorage`** → `workflowStorageWrite` and **`workflowStep`** → `workflowEvents`. Any client code that reads or references these fields by their old names will break, as the old keys no longer exist in the schema.","8f6e182206206e0c6dbe5c9815af21cf2412ab6d95dbaf445495f875c041247c","2026-06-29T22:00:34.771Z","2026-06-29-two-usage-record-field-keys-renamed-in-response-schema",{"id":312,"severity":81,"title":313,"summary":314,"contentHash":315,"detectedAt":316,"slug":317},"01KWAJYFP6PSV6KEBTW6TZQJ5G","Subscription intent output schema restructured; effectiveBehavior now required","The `output` object for subscription plan-change intents has been significantly restructured. The `changedResources` items previously used a `oneOf` with four distinct typed variants (`set_plan_item_quantity`, `increase_plan_item_quantity`, `decrease_plan_item_quantity`, `adjust_plan_item_quantity`) — each with its own `type` discriminator and `required` fields — and have been collapsed into a single unified object schema. The `type` discriminator field is gone, `resourceIds` semantics changed, and the new field **`effectiveBehavior`** (`\"end_of_term\" | \"immediate\"`) has been added to the `output` required fields, meaning any client that previously relied on the `oneOf` variant shapes or omitted `effectiveBehavior` will break.","e6aa4f01df61f22eca4e6dc506c643c315a0590ac633014bec0d6ecc714bd319","2026-06-29T21:00:45.638Z","2026-06-29-subscription-intent-output-schema-restructured",{"id":319,"severity":25,"title":320,"summary":321,"contentHash":322,"detectedAt":323,"slug":324},"01KWAFG9HFY8J1BA54B53B211S","Add rolling release start endpoint and firewall config promoted event","Added new `POST \u002Fv1\u002Fprojects\u002F{idOrName}\u002Frolling-release\u002Fstart` endpoint to initiate rolling releases for deployments, with full response schema including rolling release state tracking. Also added `team-firewall-config-promoted` as a new allowed audit event type in three event enum definitions. These are purely additive changes that do not affect existing integrations.","3010f5951a5f1929b36461f9385658dbda5070fc432b7c36702d9109bdced4db","2026-06-29T20:00:34.863Z","2026-06-29-add-rolling-release-start-endpoint-and-firewall-config",{"id":326,"severity":25,"title":327,"summary":328,"contentHash":329,"detectedAt":330,"slug":331},"01KWAC2A4H8X5RDX67V2A62P21","Add read:project-flags auth scope","The `read:project-flags` OAuth scope has been added to five API endpoint definitions in the OpenAPI specification. This is an additive change that enables new authentication permissions for accessing project flags; existing integrations with other scopes will continue to work unchanged.","000e17dfbc10fcc7528621d9e91cbcab29366e37838f77667a5503178cd12d59","2026-06-29T19:00:30.993Z","2026-06-29-add-read-project-flags-auth-scope",{"id":333,"severity":25,"title":334,"summary":335,"contentHash":336,"detectedAt":337,"slug":338},"01KWA8MJ6DMMFSS2WRDF160CCH","Add firewall and connector response fields to Vercel API","The diff adds new optional fields to Vercel API responses: **`isConnectedToPrioritizedProject`** (boolean) on connector list responses, **`configVersion`** (string or number) on firewall event payloads, and a new event type **`team-firewall-config-modified`** for webhook subscriptions. The change removes `crs` from the required fields list on firewall configuration objects. These additions enable clients to distinguish prioritized project connectors and track firewall configuration changes without breaking existing integrations.","4456b5184e027fee41c49a3f89bf7a799a7d26194f275f9275663d77ae2dbfb3","2026-06-29T18:00:34.765Z","2026-06-29-add-firewall-and-connector-response-fields-to-vercel-api",{"id":340,"severity":25,"title":341,"summary":342,"contentHash":343,"detectedAt":344,"slug":345},"01KWA56RE43NQFAPHA92GJNWX8","Add securityConfig field and vcr-repository-deleted event type","The Vercel API adds two new optional response fields: a `securityConfig` array field across multiple ACL-related schemas, and a new `vcr-repository-deleted` event type to webhook event enums. These are purely additive changes that extend the API surface without breaking existing integrations.","56a07bcd7e56bc588d77bf3812e96ac38febe1521d431df5312caa0a4fa475d1","2026-06-29T17:00:36.676Z","2026-06-29-add-securityconfig-field-and-vcr-repository-deleted-event",{"id":347,"severity":25,"title":348,"summary":349,"contentHash":350,"detectedAt":351,"slug":352},"01KWA1RX74X2QGE4AJEQ08W4XQ","Add serviceName field and AI metrics fields to function config","The diff adds a new optional `serviceName` field to function configuration objects across multiple endpoints, and adds several new fields (`chatId`, `messageId`, `inputTokens`, `outputTokens`, `timestamp`, and an `events` array) to an AI event payload schema. All new fields appear to be response fields and do not remove or alter existing functionality, making this purely additive.","6f7c2c1b8897e29ffb5678c2d204e0a048ba109a753ca1f7014260362ec75721","2026-06-29T16:00:37.092Z","2026-06-29-add-servicename-field-and-ai-metrics-fields-to-function",{"id":354,"severity":25,"title":355,"summary":356,"contentHash":357,"detectedAt":358,"slug":359},"01KW9D5H27G4B0926W8S8PX00K","Add surchargeCostCurrency and gatewayCostCurrency fields","Two new optional string fields, `surchargeCostCurrency` and `gatewayCostCurrency`, have been added to multiple response schemas in the Vercel API. These fields are purely additive and cannot break existing integrations that do not use them.","293f62af39ee3a4f7ce642ad925223a464f9ea0b35f26374821f4d96c52c43d0","2026-06-29T10:00:30.535Z","2026-06-29-add-surchargecostcurrency-and-gatewaycostcurrency-fields",{"id":361,"severity":25,"title":362,"summary":363,"contentHash":364,"detectedAt":365,"slug":366},"01KW361B5F1YH005DADH08RVNR","Add domain-zone-change-internal event type and payload fields","The Vercel API adds a new event type **`domain-zone-change-internal`** and expands the payload schema for domain zone change events. New optional fields `zone`, `domain`, `initiator`, `source`, and `previousZone` are now documented for domain zone change event payloads. These are purely additive changes that extend the webhook event system without altering existing event types or breaking client code.","8baa33bb75fe97f61207dae8eeedc5bca9e968fcd5d1aa673872b5282ec9adb7","2026-06-27T00:00:26.799Z","2026-06-27-add-domain-zone-change-internal-event-type-and-payload",{"id":368,"severity":25,"title":369,"summary":370,"contentHash":371,"detectedAt":372,"slug":373},"01KW2RA3C569YZREGQEM1W957M","Add AI Gateway ACL permissions and fields","The Vercel API adds three new team permissions — `AiGatewayApiKeyOwnedBySelf`, `AiGatewayCredits`, and `AiGatewaySettings` — along with corresponding optional ACL resource fields (`aiGatewayApiKey`, `aiGatewayApiKeyOwnedBySelf`, `aiGatewayCredits`, `aiGatewaySettings`) across multiple schema definitions. These additions enable fine-grained access control for AI Gateway features and are purely additive changes that do not affect existing behavior.","5765cde6c6458654dd7105c7c36bfa25cb21e91a2069b33e35b48f0581cab9cf","2026-06-26T20:00:33.669Z","2026-06-26-add-ai-gateway-acl-permissions-and-fields"]