GitLab 17.0 shipped with 80 breaking changes. GitLab 18.0 had 27. The upcoming GitLab 19.0 release is projected to include 15. We know that managing breaking changes across a major upgrade is time-consuming: It requires investigation and coordination across your organization. In response, we introduced a breaking change approval requirement that mandates impact mitigation and leadership sign-off before any breaking change can proceed. That process is working, and we're committed to continuing to drive that number down. Below you'll find every breaking change in GitLab 19.0, organized by deployment type and impact, alongside the mitigation steps you need to upgrade with confidence. Deployment windows Here are the deployment windows you need to know. GitLab.com Breaking changes for GitLab.com will be limited to these two windows: May 4–6, 2026 (09:00–22:00 UTC) — primary window May 11–13, 2026 (09:00–22:00 UTC) — contingency fallback Many other changes will continue to roll out throughout the month.…