data field type constraints removed, now accepts any type
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 data field previously declared a oneOf constraint accepting integer, number, string, or boolean types; that constraint has been removed, leaving only nullable: true. This is a schema loosening on the spec side, but clients that relied on the documented type union for validation or code generation will now see an untyped/any field, which could break generated SDK models or strict validators expecting a known type.