Breaking change deployments on GitLab.com
Changes are deployed continuously to GitLab.com. However, breaking changes can require more time to prepare for.
In the month before the GitLab 18.0 release, breaking changes will be deployed during three time windows. The following tables list when each breaking change will be deployed.
Window 1
This window takes place on April 21 - 23, 2025 from 09:00 UTC to 22:00 UTC.
Window 2
This window takes place on April 28 - 30, 2025 from 09:00 UTC to 22:00 UTC.
Deprecation | Impact | Stage | Scope |
---|---|---|---|
Replace GraphQL field take_ownership_pipeline_schedule with admin_pipeline_schedule in PipelineSchedulePermissions
|
Low | Verify | Project |
The heroku/builder:22 image is deprecated
|
Medium | Deploy | Project |
ciUsedMinutes GraphQL field renamed to ciDuration
|
Medium | Verify | Instance |
mergeTrainIndex and mergeTrainsCount GraphQL fields deprecated
|
Low | Verify | Project |
Pipeline subscriptions | Medium | Verify | Project |
Window 3
This window takes place on May 5 - 7, 2025 from 09:00 UTC to 22:00 UTC.
Deprecation | Impact | Stage | Scope |
---|---|---|---|
ZenTao integration | Low | Foundations | Instance |
The ci_job_token_scope_enabled projects API attribute is deprecated
|
Low | Govern | Project |
The direction GraphQL argument for ciJobTokenScopeRemoveProject is deprecated
|
Low | Govern | Project |
Replace threshold with maxretries for container registry notifications
|
Low | Package | Project |
ciJobTokenScopeAddProject GraphQL mutation is deprecated
|
Low | Govern | Project |
Guest users can pull packages from private projects on GitLab.com | High | Package | Project |
Removal of migrationState field in ContainerRepository GraphQL API
|
Low | Package | Project |
Remove previousStageJobsOrNeeds from GraphQL
|
Verify |