GitLab REST API
- REST API OpenAPI v3
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 24, 2026, 8:33 PMLast change detected Oct 24, 2026, 2:23 AM
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.
- BreakingRequest property became not nullable: delete_security_scan_profiles
openapi:POST /api/v4/member_roles::request.application.json.delete_security_scan_profiles - BreakingRequest property became not nullable: create_security_scan_profiles
openapi:POST /api/v4/member_roles::request.application.json.create_security_scan_profiles - BreakingRequest property became not nullable: archive_project
openapi:POST /api/v4/member_roles::request.application.json.archive_project - BreakingRequest property became not nullable: apply_security_scan_profiles
openapi:POST /api/v4/member_roles::request.application.json.apply_security_scan_profiles - BreakingRequest property became not nullable: admin_web_hook
openapi:POST /api/v4/member_roles::request.application.json.admin_web_hook - BreakingRequest property became not nullable: admin_vulnerability
openapi:POST /api/v4/member_roles::request.application.json.admin_vulnerability - BreakingRequest property became not nullable: admin_terraform_state
openapi:POST /api/v4/member_roles::request.application.json.admin_terraform_state - BreakingRequest property became not nullable: admin_security_attributes
openapi:POST /api/v4/member_roles::request.application.json.admin_security_attributes - BreakingRequest property became not nullable: admin_runners
openapi:POST /api/v4/member_roles::request.application.json.admin_runners - BreakingRequest property became not nullable: admin_push_rules
openapi:POST /api/v4/member_roles::request.application.json.admin_push_rules
Coverage
What Detektu monitors
Official products and contracts checked for changes.
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.