Time to Bail · Boarding pass
Act. You can stay.
After April 30, 2027 you cannot deploy Node.js 22 apps on App Engine. They keep serving traffic.[1]
Act means: change a setting or plan before the date. You can stay.
App Engine Node.js 22 runtime: support ends April 30, 2027
Google ends support for Node.js 22 on the App Engine standard environment on April 30, 2027. Apps keep running. But you can no longer deploy new versions on it, and it gets no security fixes.
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.
Check the runtime line in each app.yaml, or the runtime of each service and version in the console.
Set runtime to nodejs24 in app.yaml and update your dependencies.
Deploy each service on the new runtime before April 30, 2027.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| End of support | April 30, 2027[1] |
|---|---|
| Runtime | Node.js 22 (runtime ID nodejs22) in the App Engine standard environment[1] |
| After end of support | Your app keeps running and serving traffic, but you can no longer create or update it on this runtime[2] |
| Security fixes | Google no longer applies security updates or patches to the runtime[2] |
| Exception | An organization policy can re-enable deployments until the runtime is deprecated[2] |
| Deprecated | April 30, 2028[1] |
| Can the dates change? | Google says key dates might be delayed[1] |
| Older Node.js runtime | Node.js 20: support ended April 30, 2026; deprecated April 30, 2027, when the re-enable exception goes away[1] |
| Newer runtimes | nodejs24 ends support April 30, 2028[1] |
| Apps on Node.js 22 | Cannot be deployed again after April 30, 2027 without an exception[1] |
Your Node.js 22 app still runs and serves traffic. But you cannot create or update it on this runtime any more. Google sends no more security fixes for it.
runtime: in app.yaml to nodejs24.Source: [1] App Engine standard environment support schedule (Google Cloud) · [2] App Engine runtime lifecycle (Google Cloud)
Check it yourself. Every fact above links here.
Time to bail on App Engine apps on Node.js 22? Act. You can stay. After April 30, 2027 you cannot deploy Node.js 22 apps on App Engine. They keep serving traffic.
On our scale this is Act: change a setting or plan before the date. You can stay.
Google ends support for Node.js 22 on the App Engine standard environment on April 30, 2027. Apps keep running. But you can no longer deploy new versions on it, and it gets no security fixes.
Here are the facts we checked:
You can stay on App Engine. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Google Cloud is the main source for this page. App Engine has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Apps on Node.js 22: Cannot be deployed again after April 30, 2027 without an exception.
The date to remember is April 30, 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 App Engine apps on Node.js 22 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.