[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-13-remove-required-version-field-from-project-expiry-lock":3},{"source":4,"alert":10},{"id":5,"displayName":6,"vendor":7,"apiType":8,"url":9},"vercel-changelog","Vercel API","vercel","rest","https:\u002F\u002Fopenapi.vercel.sh\u002F",{"id":11,"slug":12,"severity":13,"title":14,"summary":15,"detectedAt":16},"01KRH07FNRZVVGT67VJJEXKWYG","2026-05-13-remove-required-version-field-from-project-expiry-lock","Breaking","Remove required `version` field from project expiry\u002Flock response schemas","The **`version`** field has been removed from two response object schemas — the scheduled-expiry object (previously required alongside `expiresAt`) and the locked object (previously required alongside `lockedAt` and `lockedBy`) — across 6 endpoint definitions. Clients that read and depend on `version` (e.g. to track `ExpireProject` event versioning or to seed a re-schedule counter) will no longer receive it, which is a breaking change for those integrations.","2026-05-13T15:45:31.320Z"]