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 25, 2026, 8:35 AMLast 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.
- InfoRequest property enum value added: name (development, other, production, staging (+1 more))
openapi:POST /api/v4/groups/{}/protected_environments::request.application.json.name - InfoRequest parameter property enum value added: environment_tiers (development, other, production, staging (+1 more))
openapi:GET /api/v4/groups/{}/dora/metrics::query.environment_tiers - InfoRequest parameter enum value added: metric (change_failure_rate, deployment_frequency, lead_time_for_changes, time_to_restore_service)
openapi:GET /api/v4/groups/{}/dora/metrics::query.metric - InfoRequest parameter enum value added: interval (all, daily, monthly)
openapi:GET /api/v4/groups/{}/dora/metrics::query.interval - InfoResponse optional property added: pipeline_cancel_limit_per_user_project
openapi:PUT /api/v4/application/settings::response.200.application.json.pipeline_cancel_limit_per_user_project - InfoNew optional request property: pipeline_cancel_limit_per_user_project
openapi:PUT /api/v4/application/settings::request.application.json.pipeline_cancel_limit_per_user_project - InfoResponse optional property added: pipeline_cancel_limit_per_user_project
openapi:GET /api/v4/application/settings::response.200.application.json.pipeline_cancel_limit_per_user_project - InfoApi schema removed: RequestBody_e90c1c6d2220
openapi:* *::schema.RequestBody_e90c1c6d2220 - InfoApi schema removed: RequestBody_9ea558c599b9
openapi:* *::schema.RequestBody_9ea558c599b9 - InfoApi schema removed: RequestBody_43af6c439096
openapi:* *::schema.RequestBody_43af6c439096
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.