createdAt and readyState moved to required in deployments response
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
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/example on createdAt is a minor documentation regression.