GCPRetirement
Cloud Run: Python 3.11 decommission
Decommission date for Python 3.11 on Cloud Run: 24 Apr 2028. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.
Retires , 24 Apr 2028
What breaks
The decommission date of Python 3.11 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.
- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.
- After the decommission date, workloads can no longer be created or updated using the runtime.
- Workloads that continue to use a decommissioned runtime may be disabled.
- A decommissioned runtime receives no language, system package or OS patches.
- Runtime customer support already ends at deprecation ("Customer support" row of the lifecycle table).
What to do
- Migrate workloads that use the runtime to a more up-to-date runtime from the support schedule. Google advises doing this during the deprecation period.
- After the decommission date, a more up-to-date runtime is required to deploy workloads.
Replacement
Not stated by vendor.
Sources
- Official sourcedocs.cloud.google.comOfficial
Last checked against this source on .
Related
- , 21 Aug 2026Cloud Run: Go 1.23 decommissionSource
- , 30 Sep 2026Cloud Run: Ruby 3.2 decommissionSource
- , 30 Oct 2026Cloud Run: Node.js 20 decommissionSource
- , 2 Mar 2027Cloud Run: Go 1.24 decommissionSource
- , 1 Apr 2027Cloud Run: Go 1.25 decommissionSource
- , 4 Apr 2027Cloud Run: Python 3.10 decommissionSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item