timetobail

GitHub · Forced move · Announced October 2, 2026 · Sources checked Oct 17

Time to bail on GitHub Apps that send the stateless token header?

Time to Bail · Boarding pass

FromGitHub Apps that send the stateless token header
ToYour pick

Check. You can stay.

GitHub ignores the header from November 30, 2026. Apps that use it to get old tokens get new ones.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Header no longer respected
Time left
43days
Status
Act

GitHub App token format header stops working November 30, 2026

GitHub App tokens now have a new, longer format. They are about 520 characters, not 40. A test header, X-GitHub-Stateless-S2S-Token, let apps ask for the old kind. From November 30, 2026, GitHub ignores it. Then apps get only the new tokens.

Email me 7 days before Nov 30

One email with the first steps. Nothing else.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

How it is winding down

  1. Oct 2AnnouncedDone
  2. Nov 30Header no longer respectedNext

What to do before November 30

Tick steps as you go. Your progress stays in this browser.

  1. Find the header

    Search your code for X-GitHub-Stateless-S2S-Token.

  2. Make room for long tokens

    Check database columns, secret stores, proxies and log filters. Tokens are about 520 characters now.

  3. Remove the header

    Delete it once your app works with the new tokens.

Email me 7 days before Nov 30

One email with the first steps. Nothing else.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
Header no longer respectedNovember 30, 2026[1]
New installation tokenStarts with ghs_, about 520 characters long instead of 40[1]
HeaderX-GitHub-Stateless-S2S-Token on POST /app/installations/:installation_id/access_tokens[2]
What the disabled value didReturned a classic opaque token, even after the rollout reached the app[2]
Pattern GitHub suggests for both formatsghs_[A-Za-z0-9\.\-_]{36,}[2]
StorageDatabase columns and header settings must accept at least 520 characters[2]
Tokens made beforeKeep working until they expire[1]
GitHub Enterprise ServerNot affected[2]
AnnouncedOctober 2, 2026[1]
Apps that send the headerGet stateless tokens after November 30, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. Stateless GitHub App installation tokens rolled out GitHub · primary · checked Oct 17
  2. GitHub App installation tokens: Per-request override header GitHub · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on GitHub Apps that send the stateless token header? Check. You can stay. GitHub ignores the header from November 30, 2026. Apps that use it to get old tokens get new ones.

On our scale this is Act: change a setting or plan before the date. You can stay.

GitHub App tokens now have a new, longer format. They are about 520 characters, not 40. A test header, X-GitHub-Stateless-S2S-Token, let apps ask for the old kind. From November 30, 2026, GitHub ignores it. Then apps get only the new tokens.

Here are the facts we checked:

  • Header no longer respected: November 30, 2026 (GitHub)
  • New installation token: Starts with ghs_, about 520 characters long instead of 40 (GitHub)
  • Header: X-GitHub-Stateless-S2S-Token on POST /app/installations/:installation_id/access_tokens (GitHub)
  • What the disabled value did: Returned a classic opaque token, even after the rollout reached the app (GitHub)
  • Pattern GitHub suggests for both formats: ghs_[A-Za-z0-9\.\-_]{36,} (GitHub)
  • Storage: Database columns and header settings must accept at least 520 characters (GitHub)
  • Tokens made before: Keep working until they expire (GitHub)
  • GitHub Enterprise Server: Not affected (GitHub)
  • Announced: October 2, 2026 (GitHub)
  • Apps that send the header: Get stateless tokens after November 30, 2026 (GitHub)

You can stay on GitHub. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

GitHub is the main source for this page. GitHub has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Apps that send the header: Get stateless tokens after November 30, 2026.

The date to remember is November 30, 2026. Make the change before then.

What to do before November 30

  1. Find the header. Search your code for X-GitHub-Stateless-S2S-Token.
  2. Make room for long tokens. Check database columns, secret stores, proxies and log filters. Tokens are about 520 characters now.
  3. Remove the header. Delete it once your app works with the new tokens.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

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.

Options people mention

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.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on GitHub Apps that send the stateless token header 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.