Remove required constraint on 'city' and mark it nullable
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 city field in the ContactInformation-adjacent schema (likely a location/address object) has had its required constraint removed and is now marked nullable: true. This is a breaking change for clients that rely on city always being present in responses — code that accesses city without a null check may now encounter null or a missing field. Clients sending requests that previously relied on server-side validation rejecting missing city values will also see different behaviour.