timetobail
My stack

Heroku · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Heroku apps on the Heroku-22 stack?

Time to Bail · Boarding pass

FromHeroku apps on the Heroku-22 stack
ToYour pick

Act. You can stay.

From November 1, 2026, some Heroku-22 builds fail on purpose. All builds stop May 1, 2027.[1]

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

Gate closes
Builds start failing
Time left
16days
Status
Act

Heroku-22 stack: builds start failing November 1, 2026

From November 1, 2026, Heroku makes some builds of Heroku-22 apps fail on purpose. It happens more often over time. From May 1, 2027, no Heroku-22 builds run at all. Heroku grants no extensions.

How it is winding down

  1. Nov 1, 2026Builds start failingNext
  2. Apr 30End of life
  3. May 1All builds stop

What to do before November 1

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

  1. List your Heroku-22 apps

    Install the apps-table CLI plugin, then run heroku apps:table --filter="STACK=heroku-22".

  2. Move each app to Heroku-24 or Heroku-26

    Set the new stack and fix buildpack or native library issues in a test app first.

  3. Deploy before the failures start

    Finish before November 1, 2026 so your deploys do not fail at a bad time.

Facts we checked

Facts and their sources
Builds start failingNovember 1, 2026[1]
First stageFrom November 1, 2026 the first build in each 30-day period fails[1]
ThenFrom February 1, 2027 the first build in each 7-day period fails[1]
ThenFrom April 1, 2027 the first build in each 24-hour period fails[1]
End of lifeApril 30, 2027[1]
All builds stopMay 1, 2027, including Review Apps and Heroku CI[1]
ExtensionsNone. Heroku says it is unable to grant extensions[1]
Stacks to move toHeroku-24 (supported to April 2029) or Heroku-26 (supported to April 2031)[2]
How to list your Heroku-22 appsheroku apps:table --filter="STACK=heroku-22" (with the apps-table plugin)[1]
Apps still on Heroku-22Builds fail from November 1, 2026 and stop on May 1, 2027[1]

Sources

Check it yourself. Every fact above links here.

  1. Heroku-22 end-of-life FAQ Heroku · primary · checked Oct 13
  2. Stacks Heroku · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Heroku apps on the Heroku-22 stack? Act. You can stay. From November 1, 2026, some Heroku-22 builds fail on purpose. All builds stop May 1, 2027.

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

From November 1, 2026, Heroku makes some builds of Heroku-22 apps fail on purpose. It happens more often over time. From May 1, 2027, no Heroku-22 builds run at all. Heroku grants no extensions.

Here are the facts we checked:

  • Builds start failing: November 1, 2026 (Heroku)
  • First stage: From November 1, 2026 the first build in each 30-day period fails (Heroku)
  • Then: From February 1, 2027 the first build in each 7-day period fails (Heroku)
  • Then: From April 1, 2027 the first build in each 24-hour period fails (Heroku)
  • End of life: April 30, 2027 (Heroku)
  • All builds stop: May 1, 2027, including Review Apps and Heroku CI (Heroku)
  • Extensions: None. Heroku says it is unable to grant extensions (Heroku)
  • Stacks to move to: Heroku-24 (supported to April 2029) or Heroku-26 (supported to April 2031) (Heroku)
  • How to list your Heroku-22 apps: heroku apps:table --filter="STACK=heroku-22" (with the apps-table plugin) (Heroku)
  • Apps still on Heroku-22: Builds fail from November 1, 2026 and stop on May 1, 2027 (Heroku)

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

Leaving is a choice here, not a must.

Heroku is the main source for this page. Heroku 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 still on Heroku-22: Builds fail from November 1, 2026 and stop on May 1, 2027.

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

What to do before November 1

  1. List your Heroku-22 apps. Install the apps-table CLI plugin, then run heroku apps:table --filter="STACK=heroku-22".
  2. Move each app to Heroku-24 or Heroku-26. Set the new stack and fix buildpack or native library issues in a test app first.
  3. Deploy before the failures start. Finish before November 1, 2026 so your deploys do not fail at a bad time.

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 Heroku apps on the Heroku-22 stack 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.

Open the playbookList your product