Playbook: GitLab legacy CI/CD job token format ends in 20.0 (May 20, 2027)

3 Reply templates

Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

Helpful first

Sorry you have to deal with this. You can stay on GitLab. Here is what to change before May 20, 2027:

1. Check the group setting. In the top-level group, open Settings > CI/CD > General pipelines. See if JWT format is off.
2. Fix base64 in scripts. Change base64 to base64 -w0 wherever a script encodes CI_JOB_TOKEN.
3. Update the Fargate executor. Use version 0.5.1 or later of the AWS Fargate custom executor.

If they would rather leave, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]

Short answer

You have until May 20, 2027. You can stay on GitLab. First: check the group setting. Then fix base64 in scripts.
Happy to help if you get stuck.
[Disclosure: I build <your product>.]

4 Switch-page builder

Create a draft “Switch from GitLab” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

Add your product name to replace “Your product”.

Preview

Switch from GitLab to Your product

GitLab groups that still use legacy job tokens: a change is due by May 20. You can stay on GitLab. If you would rather leave, here is how to move to Your product.

What changes at GitLab

Since GitLab 19.0, CI/CD job tokens use the JWT format by default. A top-level group can still switch back to the legacy format, but only until the GitLab 20.0 release, planned for May 20, 2027. The longer JWT tokens break scripts that pipe the token to base64 without -w0.

GitLab 20.0 release (planned): May 20, 2027 (GitLab)
JWT format by default since: GitLab 19.0 (GitLab)
Legacy format setting: Turn off Enable JWT format for CI/CD job tokens in the top-level group; only until the GitLab 20.0 release (GitLab)
Known issue: base64: base64 wraps the long token and makes it invalid; use base64 -w0 (GitLab)
Error you may see: invalid character '\n' in string literal (GitLab)
Known issue: AWS Fargate: The Fargate custom executor 0.5.0 and earlier fails; upgrade to 0.5.1 or later (GitLab)
Groups on the legacy format: Move to JWT tokens with GitLab 20.0 (GitLab)

You can stay on GitLab if you make the change. This page is for people who would rather leave.

What Your product gives you

Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

How to move from GitLab to Your product

Save what you need from GitLab. Keep a copy before you cancel anything.
Import into Your product. Say which files you accept and how long an import takes.

Tell readers the key date: May 20, 2027.

Questions people ask

If Your product has a direct answer to one of these, add it here. Keep it short and true.

How to help new users settle in

Send one short email. Say what changed, where to find you now, and what they need to do. 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.

Sources

Deprecations and removals by version — GitLab (primary), checked 2026-10-17
GitLab release and maintenance policy — GitLab (primary), checked 2026-10-17
GitLab CI/CD job token — GitLab (primary), checked 2026-10-17

GitLab legacy CI/CD job token format ends in 20.0 (May 20, 2027)

1 Related discussions

2 What people ask