detektu
Supported APIs

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 Nov 15, 2026, 6:10 AMLast change detected Nov 13, 2026, 11:58 PM

Monitor GitLab freeDeprecation 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.

  1. Info
    Api schema removed: RequestBody_0f8617d6f179openapi:* *::schema.RequestBody_0f8617d6f179
    GitLab REST API
  2. Info
    Api schema removed: RequestBody_06a0cb5a3ce3openapi:* *::schema.RequestBody_06a0cb5a3ce3
    GitLab REST API
  3. Potentially breaking
    Response optional property removed: weightopenapi:GET /api/v4/vulnerabilities/{}/issue_links::response.200.application.json.weight
    GitLab REST API
  4. Potentially breaking
    Response optional property removed: web_urlopenapi:GET /api/v4/vulnerabilities/{}/issue_links::response.200.application.json.web_url
    GitLab REST API
  5. Potentially breaking
    Response optional property removed: vulnerability_link_typeopenapi:GET /api/v4/vulnerabilities/{}/issue_links::response.200.application.json.vulnerability_link_type
    GitLab REST API
  6. Potentially breaking
    Response optional property removed: vulnerability_link_idopenapi:GET /api/v4/vulnerabilities/{}/issue_links::response.200.application.json.vulnerability_link_id
    GitLab REST API
  7. Potentially breaking
    Response optional property removed: user_notes_countopenapi:GET /api/v4/vulnerabilities/{}/issue_links::response.200.application.json.user_notes_count
    GitLab REST API
  8. Potentially breaking
    Response optional property removed: upvotesopenapi:GET /api/v4/vulnerabilities/{}/issue_links::response.200.application.json.upvotes
    GitLab REST API
  9. Potentially breaking
    Response optional property removed: updated_atopenapi:GET /api/v4/vulnerabilities/{}/issue_links::response.200.application.json.updated_at
    GitLab REST API
  10. Potentially breaking
    Response optional property removed: typeopenapi:GET /api/v4/vulnerabilities/{}/issue_links::response.200.application.json.type
    GitLab REST API

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