Vendor coverage

GitLab API changes & breaking changes

GitLab announces deprecations continuously but concentrates breaking API changes into its annual major release each May. Detektu diffs the published REST API spec so the bundle of removals never lands unreviewed.

Last checked Oct 20, 2026, 7:40 PMLast change detected Oct 20, 2026, 1:40 PM

Monitor GitLab free Deprecation calendar

Detected changes

Latest GitLab API changes

Every entry is a change Detektu detected in GitLab's published contracts, with exact before/after evidence on its page.

Info
Response optional property added: invalid_approvers_rulesopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.invalid_approvers_rules
GitLab REST APIOct 17, 2026
Info
Response optional property added: iidopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.iid
GitLab REST APIOct 17, 2026
Info
Response optional property added: idopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.id
GitLab REST APIOct 17, 2026
Info
Response optional property added: has_approval_rulesopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.has_approval_rules
GitLab REST APIOct 17, 2026
Info
Response optional property added: created_atopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.created_at
GitLab REST APIOct 17, 2026
Info
Response optional property added: approversopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.approvers
GitLab REST APIOct 17, 2026
Info
Response optional property added: approver_groupsopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.approver_groups
GitLab REST APIOct 17, 2026
Info
Response optional property added: approvals_requiredopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.approvals_required
GitLab REST APIOct 17, 2026
Info
Response optional property added: approvals_leftopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.approvals_left
GitLab REST APIOct 17, 2026
Info
Response optional property added: approval_rules_leftopenapi:GET /api/v4/projects/{}/merge_requests/{}/approvals::response.200.application.json.approval_rules_left
GitLab REST APIOct 17, 2026

Coverage

What Detektu monitors

Official products and contracts checked for changes.

GitLab REST API

REST API OpenAPI v3OpenAPI contractStable

Change model

How GitLab ships changes

The release patterns that shape your integration risk.

GitLab's REST API (v4) evolves additively during the year, with deprecations announced per milestone and removals reserved for major releases like 17.0 and 18.0. That model is friendly, provided you review the deprecation list. In practice, the list is long and mostly irrelevant to any one integration.

Detektu turns the spec diff into per-endpoint findings and matches them against your declared usage, so the yearly removal bundle becomes a short, reviewed list instead of a release-day scramble.

Monitored for you

Do GitLab's changes affect your integration?

Choose the operations and fields your services use. Detektu matches GitLab findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.

Monitor GitLab free See pricing