Remove required fields 'brief' and 'isDeprecated' from context object
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 required constraint on the context response object has been removed, meaning brief and isDeprecated are no longer guaranteed to be present. Clients that assumed these fields were always present (e.g. accessing them without null-checks) may encounter runtime errors. The description update clarifies that custom attributes now receive an empty context, which explains why these fields can no longer be required.