membership field removed from required fields in two team/project response schemas
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 membership field has been removed from the required array in two distinct response object schemas (one appears to be a team/project schema around line 167344, another around line 167679). Clients that currently expect membership to always be present in these response objects may break if they treat its absence as an error, or if SDK-generated code enforces required-field validation.