timetobail
My stack

Cloud Run functions · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Cloud Run functions on Node.js 20?

Time to Bail · Boarding pass

FromCloud Run functions on Node.js 20
ToYour pick

Act. You can stay.

After October 30, 2026, Node.js 20 functions cannot be created or updated, and may be disabled.[1]

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

Gate closes
Decommission date
Time left
14days
Status
Act

Node.js 20 functions on Google Cloud: decommissioned October 30, 2026

Google decommissions the Node.js 20 runtime for Cloud Run functions on October 30, 2026. After that you cannot create or update these functions, and they may be disabled.

How it is winding down

  1. Apr 30Deprecated sinceDone
  2. Oct 30Decommission dateNext

What to do before October 30

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

  1. Find functions on Node.js 20

    In the console, check the runtime of each function. Note every one on Node.js 20.

  2. Change the runtime

    Set the runtime to Node.js 22 or Node.js 24 and update your packages. Node.js 24 is supported longer.

  3. Deploy each function again

    Deploy and test every function before October 30.

Facts we checked

Facts and their sources
Decommission dateOctober 30, 2026[1]
RuntimeNode.js 20 (Cloud Run functions and Cloud Functions 1st gen)[1]
Deprecated sinceApril 30, 2026[1]
After decommissionYou can no longer create new workloads or update existing ones on the runtime[1]
If you do nothingFunctions that stay on a decommissioned runtime may be disabled[1]
Next runtime endsNode.js 22 is decommissioned October 31, 2027[1]
Newest runtime endsNode.js 24 is decommissioned October 31, 2028[1]
Functions still on Node.js 20Cannot be updated after October 30, 2026 and may be disabled[1]

Sources

Check it yourself. Every fact above links here.

  1. Cloud Run functions runtime support Google Cloud · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Cloud Run functions on Node.js 20? Act. You can stay. After October 30, 2026, Node.js 20 functions cannot be created or updated, and may be disabled.

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

Google decommissions the Node.js 20 runtime for Cloud Run functions on October 30, 2026. After that you cannot create or update these functions, and they may be disabled.

Here are the facts we checked:

  • Decommission date: October 30, 2026 (Google Cloud)
  • Runtime: Node.js 20 (Cloud Run functions and Cloud Functions 1st gen) (Google Cloud)
  • Deprecated since: April 30, 2026 (Google Cloud)
  • After decommission: You can no longer create new workloads or update existing ones on the runtime (Google Cloud)
  • If you do nothing: Functions that stay on a decommissioned runtime may be disabled (Google Cloud)
  • Next runtime ends: Node.js 22 is decommissioned October 31, 2027 (Google Cloud)
  • Newest runtime ends: Node.js 24 is decommissioned October 31, 2028 (Google Cloud)
  • Functions still on Node.js 20: Cannot be updated after October 30, 2026 and may be disabled (Google Cloud)

You can stay on Cloud Run functions. 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. Cloud Run functions 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

Functions still on Node.js 20: Cannot be updated after October 30, 2026 and may be disabled.

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

What to do before October 30

  1. Find functions on Node.js 20. In the console, check the runtime of each function. Note every one on Node.js 20.
  2. Change the runtime. Set the runtime to Node.js 22 or Node.js 24 and update your packages. Node.js 24 is supported longer.
  3. Deploy each function again. Deploy and test every function before October 30.

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 Cloud Run functions on Node.js 20 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