Time to Bail · Boarding pass
Act. You can stay.
Compliance pipelines are removed in GitLab 20.0, planned for May 20, 2027. Move each one to a policy first.[1]
Act means: change a setting or plan before the date. You can stay.
GitLab 20.0 removes compliance pipelines (May 20, 2027)
GitLab deprecated compliance pipelines in GitLab 17.3. They are set to be removed in GitLab 20.0, planned for May 20, 2027. GitLab asks you to move each one to a pipeline execution policy. The framework page has a button that does the move.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
Find each compliance framework that has a compliance pipeline set.
Open the framework and select Migrate pipeline to a policy.
Run a pipeline in a test project and check that the required jobs still run.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| GitLab 20.0 release (planned) | May 20, 2027[2] |
|---|---|
| Removed in | GitLab 20.0[1] |
| Deprecated in | GitLab 17.3[1] |
| Replacement | Pipeline execution policy type[1] |
| Breaking change | Yes[3] |
| How to move | In the compliance framework, select Migrate pipeline to a policy in the banner[3] |
| Before you turn on policies | Move the compliance pipeline first; do not run both in the same project[3] |
| GitLab.com | Deprecated features can be removed at any time in the month before the release[1] |
| Compliance frameworks with a compliance pipeline | Must move to a policy before GitLab 20.0[1] |
Check it yourself. Every fact above links here.
Time to bail on GitLab compliance pipelines? Act. You can stay. Compliance pipelines are removed in GitLab 20.0, planned for May 20, 2027. Move each one to a policy first.
On our scale this is Act: change a setting or plan before the date. You can stay.
GitLab deprecated compliance pipelines in GitLab 17.3. They are set to be removed in GitLab 20.0, planned for May 20, 2027. GitLab asks you to move each one to a pipeline execution policy. The framework page has a button that does the move.
Here are the facts we checked:
You can stay on GitLab. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
GitLab is the main source for this page. GitLab has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Compliance frameworks with a compliance pipeline: Must move to a policy before GitLab 20.0.
The date to remember is May 20, 2027. Make the change before then.
A few tips:
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People on GitLab compliance pipelines can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.
Listing is free. An editor checks it. Not ranked. Not paid.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.