[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-gitlab-openapi-2026-05-21-mr-sub-resource-endpoints-corrected-from-object-to-array":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"gitlab-openapi","GitLab API","gitlab","openapi-yaml","rest","https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fgitlab\u002F-\u002Fraw\u002Fmaster\u002Fdoc\u002Fapi\u002Fopenapi\u002Fopenapi_v2.yaml",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KS5DCR0SJZXY7J4N3KQD0VCK","2026-05-21-mr-sub-resource-endpoints-corrected-from-object-to-array","Breaking","MR sub-resource endpoints corrected from object to array responses; rebase returns 202","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 \u002Fapi\u002Fv4\u002Fprojects\u002F{id}\u002Fmerge_requests\u002F{merge_request_iid}\u002Frebase`) 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.","2026-05-21T14:00:23.833Z"]