MR sub-resource endpoints corrected from object to array responses; rebase returns 202
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 merge request sub-resource endpoints had their 200 response schema corrected from a single $ref object to a proper array of items — clients that assumed a single object will now receive an array. Additionally, the rebase endpoint (PUT /api/v4/projects/{id}/merge_requests/{merge_request_iid}/rebase) changed its success status code from 200 to 202, which breaks clients that check for HTTP 200. The remaining changes (added error response codes for CI config and context commits endpoints, and a reordering of definitions) are purely additive or cosmetic.