Multiple fields retyped from string to integer/object/array in audit, approval, and protected-env entities
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
Several fields across three schema definitions have had their declared types corrected/changed in ways that will break clients relying on the previous types:
API_Entities_AuditEvent:id,author_id,entity_idchanged fromstring→integer (int32);detailschanged fromstring→object;created_atgainsformat: date-time.API_Entities_ProtectedEnvironments_ApprovalRuleForSummary:id,user_id,group_id,access_level,required_approvals,group_inheritance_typeall changed fromstring→integer (int32).API_Entities_MergeRequestApprovalState(or similar approval entity):approversandapprover_groupschanged fromstring→array of objects.
Any client code that parses these fields as strings or treats approvers/approver_groups as a scalar string will break.