Breaking change deployments on GitLab.com

Changes are deployed continuously to GitLab.com. However, breaking changes can require more time to prepare for.

Breaking changes that are scheduled for the next GitLab major release (19.0) will be deployed to GitLab.com during a specific window. A contingency window (May 11 - 13, 2026) is available as a fallback if a breaking change cannot be deployed during the primary window.

This window takes place on May 4 - 6, 2026 from 09:00 UTC to 22:00 UTC.

DeprecationImpactScopeCheck potential impact
The heroku/builder:22 image is deprecatedMediumProject
ciJobTokenScopeAddProject GraphQL mutation is deprecatedLowProject
Linux package support for Ubuntu 20.04MediumInstance
Support for Redis 6LowInstance
Slack slash commandsLowInstance, group, projecthttps://gitlab.com/gitlab-org/gitlab/-/work_items/569345#am-i-impacted
Trending tab in Explore projects page is deprecatedLowProject
Using app passwords with Bitbucket Cloud import GitLab APILowProjecthttps://gitlab.com/gitlab-org/gitlab/-/work_items/588961#am-i-impacted
Linux package support for SUSE distributionsLowInstance
Enforce page limit for unauthenticated Projects API requestsLowProject
Support for NGINX IngressMediumInstance
Mattermost bundled with Linux packageLowInstance
Support for PostgreSQL 16MediumInstance
Support for bundled PostgreSQL, Redis, and MinIO in GitLab Helm chartMediumInstancehttps://docs.gitlab.com/charts/installation/migration/bundled_chart_migration/
Spamcheck support in the Linux package and GitLab Helm chartLowInstance