GitLab 19.0 Breaking Changes Guide
💡GitLab 19.0 breaking changes may break ML CI/CD pipelines—prep your self-managed infra now.
⚡ 30-Second TL;DR
What Changed
15 breaking changes in GitLab 19.0, down from 27 in 18.0
Why It Matters
Impacts self-managed users on Helm charts, requiring networking migration. GitLab.com and Dedicated have controlled windows. Fewer changes signal improved upgrade process.
What To Do Next
Audit your GitLab Helm chart for NGINX Ingress and test Envoy Gateway migration before May 2026 upgrade.
Key Points
- •15 breaking changes in GitLab 19.0, down from 27 in 18.0
- •GitLab.com deployments May 4–6 and 11–13, 2026
- •Self-Managed available May 21, 2026; Dedicated week of June 22
- •Helm chart replaces NGINX Ingress (EOL March 2026) with Envoy Gateway default
- •NGINX Ingress re-enableable until removal in GitLab 20.0
Weekly AI Recap
Read this week's curated digest of top AI events →
👉Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: GitLab Blog ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
The weekly digest
One email a week. Unsubscribe anytime.