Time to Bail · Boarding pass
Act. You can stay.
After April 4, 2027, Python 3.10 functions cannot be created or updated, and may be disabled.[1]
Act means: change a setting or plan before the date. You can stay.
Python 3.10 functions on Google Cloud: decommissioned April 4, 2027
Google decommissions the Python 3.10 runtime (python310) for Cloud Run functions on April 4, 2027. After that you cannot create or update these functions, and they may be disabled.
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.
In the console, check the runtime of each function. Note every one on python310.
Set the runtime to python312, python313 or python314 and update your dependencies.
Deploy and test every function before April 4, 2027.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| Decommission date | April 4, 2027[1] |
|---|---|
| Runtime | Python 3.10, runtime ID python310 (1st gen and Cloud Run functions)[1] |
| Deprecated since | October 4, 2026[1] |
| After decommission | You can no longer create new workloads or update existing ones on the runtime[1] |
| If you do nothing | Functions that stay on a decommissioned runtime may be disabled[1] |
| Cloud Run source deploys | The python310 runtime on Cloud Run has the same dates[2] |
| Can the dates change? | Google says key dates might be delayed[1] |
| Next Python runtime | Python 3.11: deprecated October 24, 2027; decommissioned April 24, 2028[1] |
| Newer runtimes | python312 is decommissioned April 2, 2029, python313 April 10, 2030, python314 April 10, 2031[1] |
| Functions still on Python 3.10 | Cannot be updated after April 4, 2027 and may be disabled[1] |
You can no longer create or update functions on Python 3.10. To deploy, you must pick a newer runtime. Google may disable functions left on Python 3.10.
python312, python313 or python314, then deploy again.Source: [1] Cloud Run functions runtime support (Google Cloud)
Check it yourself. Every fact above links here.
Time to bail on Cloud Run functions on Python 3.10? Act. You can stay. After April 4, 2027, Python 3.10 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 Python 3.10 runtime (python310) for Cloud Run functions on April 4, 2027. After that you cannot create or update these functions, and they may be disabled.
Here are the facts we checked:
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.
Functions still on Python 3.10: Cannot be updated after April 4, 2027 and may be disabled.
The date to remember is April 4, 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 Cloud Run functions on Python 3.10 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.