New: MCP server monitoring is live. Start free trial
GitLabSchemaAdditive

Schema reference changed in POST /api/v4/projects/{id}/merge_requests/{merge_request_iid}/context_commits response 201: "API_Entities_Commit" → "inline:array"

Affected surface
POST /api/v4/projects/{id}/merge_requests/{merge_request_iid}/context_commits

What changed

Schema reference changed in POST /api/v4/projects/{id}/merge_requests/{merge_request_iid}/context_commits response 201: "API_Entities_Commit" → "inline:array" Affected surface: POST /api/v4/projects/{id}/merge_requests/{merge_request_iid}/context_commits. Root cause: endpoint `POST /api/v4/projects/{id}/merge_requests/{merge_request_iid}/context_commits`. Detected at Thu, 21 May 2026 16:44:54 UTC UTC.

Diff

{
  "current_value": "inline:array",
  "path": "POST /api/v4/projects/{id}/merge_requests/{merge_request_iid}/context_commits",
  "previous_value": "API_Entities_Commit",
  "schema_path": "POST /api/v4/projects/{id}/merge_requests/{merge_request_iid}/context_commits response 201"
}

Likely impact

This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.

Diff your serializers against the new schema. The diff above shows what moved.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.