[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-07-16-createdat-and-readystate-moved-to-required-in-deployments":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"vercel-changelog","Vercel API","vercel","openapi-json","rest","https:\u002F\u002Fopenapi.vercel.sh\u002F",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KXNG7YEHTZF233CHNY5836W1","2026-07-16-createdat-and-readystate-moved-to-required-in-deployments","Breaking","createdAt and readyState moved to required in deployments response","The `createdAt` and `readyState` fields in the `deployments` array response were repositioned in the schema **and both added to the `required` array**. Additionally, the `description` and `example` annotations were removed from `createdAt` and `readyState` in their new positions. Making these fields required is an additive contract strengthening for consumers (they can now rely on these fields always being present), but any client-side validation or schema tools that strictly enforced the old schema (where these were optional) may behave differently. The loss of `description`\u002F`example` on `createdAt` is a minor documentation regression.","2026-07-16T13:00:50.513Z"]