Track Google Cloud Functions (Cloud Run functions) runtimes across Node.js, Python, Go, Java, Ruby, PHP, and .NET. Deprecation dates, decommission timelines, and migration guidance for every supported runtime.
Google Cloud Functions runtimes follow a three-phase lifecycle. Google provides at least 90 days notice before deprecation.
GAGenerally Available
Fully supported. Receives security patches, bug fixes, and is recommended for production workloads. New deployments and redeployments are allowed.
DeprecatedDeprecated
No longer officially supported. You can still deploy and redeploy functions, but no security patches or bug fixes are provided. Begin migration immediately.
DecommissionedDecommissioned
Cannot deploy new functions or redeploy existing ones on this runtime. Google may disable functions still running on a decommissioned runtime.
Supported Language Runtimes
All active runtimes for Cloud Run functions and 1st gen. Dates from Google Cloud documentation.
Node.js
Node.js 24
GA
Run functions nodejs24
Deprecated: 30 Apr 2028 (2.2 years)
Decommissioned: 31 Oct 2028 (2.7 years)
Latest LTS. Cloud Run functions only.
Node.js 22
GA
1st gen + Run nodejs22
Deprecated: 30 Apr 2027 (1.2 years)
Decommissioned: 31 Oct 2027 (1.7 years)
Active LTS. Available on both generations.
Node.js 20
GA
1st gen + Run nodejs20
Deprecated: 30 Apr 2026 (2 months)
Decommissioned: 30 Oct 2026 (8 months)
Maintenance LTS. Approaching deprecation.
Approaching deprecation. Plan your upgrade now.
Python
Python 3.14
GA
Run functions python314
Deprecated: 10 Oct 2030 (4.6 years)
Decommissioned: 10 Apr 2031 (5.1 years)
Latest release. Cloud Run functions only.
Python 3.13
GA
Run functions python313
Deprecated: 10 Oct 2029 (3.6 years)
Decommissioned: 10 Apr 2030 (4.1 years)
Current stable. Recommended for new projects.
Python 3.12
GA
1st gen + Run python312
Deprecated: 2 Oct 2028 (2.6 years)
Decommissioned: 2 Apr 2029 (3.1 years)
Widely deployed. Available on both generations.
Python 3.11
GA
1st gen + Run python311
Deprecated: 24 Oct 2027 (1.6 years)
Decommissioned: 24 Apr 2028 (2.1 years)
Stable. Available on both generations.
Python 3.10
GA
1st gen + Run python310
Deprecated: 4 Oct 2026 (7 months)
Decommissioned: 4 Apr 2027 (1.1 years)
Approaching deprecation. Plan upgrade to 3.12+.
Go
Go 1.26
Preview
Run functions go126
Dates pending GA
Preview. Cloud Run functions only.
Go 1.25
GA
Run functions go125
Deprecation TBD
Current stable. Cloud Run functions only.
Go 1.24
GA
Run functions go124
Deprecation TBD
Stable. Cloud Run functions only.
Go 1.23
GA
Run functions go123
Deprecated: 21 Feb 2026 (Ended 13d ago)
Decommissioned: 21 Aug 2026 (6 months)
Approaching deprecation. Upgrade to 1.24+.
Java
Java 25
GA
Run functions java25
Deprecated: 1 Oct 2031 (5.6 years)
Decommission TBD
Latest release. Cloud Run functions only.
Java 21
GA
Run functions java21
Deprecated: 1 Sep 2031 (5.5 years)
Decommission TBD
LTS. Cloud Run functions only.
Java 17
GA
1st gen + Run java17
Deprecated: 1 Oct 2027 (1.6 years)
Decommission TBD
LTS. Available on both generations.
Ruby
Ruby 3.4
GA
Run functions ruby34
Deprecated: 31 Mar 2028 (2.1 years)
Decommissioned: 30 Sep 2028 (2.6 years)
Latest release. Cloud Run functions only.
Ruby 3.3
GA
1st gen + Run ruby33
Deprecated: 31 Mar 2027 (1.1 years)
Decommissioned: 30 Sep 2027 (1.6 years)
Current stable. Available on both generations.
Ruby 3.2
GA
1st gen + Run ruby32
Deprecated: 31 Mar 2026 (25 days left)
Decommissioned: 30 Sep 2026 (7 months)
Approaching deprecation. Upgrade to 3.3+.
Approaching deprecation. Plan your upgrade now.
PHP
PHP 8.5
Preview
Run functions php85
Dates pending GA
Preview. Cloud Run functions only.
PHP 8.4
GA
Run functions php84
Deprecated: 31 Dec 2028 (2.8 years)
Decommissioned: 30 Jun 2029 (3.3 years)
Current stable. Cloud Run functions only.
PHP 8.3
GA
Run functions php83
Deprecated: 31 Dec 2027 (1.8 years)
Decommissioned: 30 Jun 2028 (2.3 years)
Widely deployed. Cloud Run functions only.
PHP 8.2
GA
1st gen + Run php82
Deprecated: 31 Dec 2026 (10 months)
Decommissioned: 30 Jun 2027 (1.3 years)
Available on both generations. Approaching deprecation.
.NET
.NET 10
GA
Run functions dotnet10
Deprecated: 14 Nov 2028 (2.7 years)
Decommissioned: 14 May 2029 (3.2 years)
LTS. Cloud Run functions only.
.NET 8
GA
Run functions dotnet8
Deprecation TBD
LTS. Cloud Run functions only.
Recently Deprecated & Decommissioned
Runtimes that have recently reached or are approaching their deprecation and decommission dates.
Runtime
Deprecated
Decommissioned
Action Required
Ruby 3.0 ruby30
31 Mar 2024
31 Mar 2025 (Ended 340d ago)
Upgrade to Ruby 3.2+
Python 3.8 python38
14 Oct 2024
14 Oct 2025 (Ended 143d ago)
Upgrade to Python 3.10+
Node.js 18 nodejs18
30 Apr 2025
30 Oct 2025 (Ended 127d ago)
Upgrade to Node.js 20 or 22
Java 11 java11
31 Oct 2024
31 Oct 2025 (Ended 126d ago)
Upgrade to Java 17 or 21
Go 1.21 go121
3 Sep 2025
3 Mar 2026 (Ended 3d ago)
Upgrade to Go 1.23+
Python 3.9 python39
5 Oct 2025
5 Apr 2026 (30 days left)
Upgrade to Python 3.10+
PHP 8.1 php81
31 Dec 2025
30 Jun 2026 (4 months)
Upgrade to PHP 8.2+
Go 1.22 go122
28 Jan 2026
28 Jul 2026 (5 months)
Upgrade to Go 1.23+
Frequently Asked Questions
Common questions about Google Cloud Functions runtimes, generations, and migration.
What is the difference between 1st gen and Cloud Run functions?
1st gen Cloud Functions is the original serverless platform from Google Cloud, running in a proprietary execution environment. Cloud Run functions (formerly "Cloud Functions 2nd gen") is built on Cloud Run and Eventarc, offering longer request timeouts (up to 60 minutes), larger instance sizes (up to 32 GiB RAM), concurrency (up to 1,000 concurrent requests per instance), traffic splitting, and over 125+ event sources. Google recommends Cloud Run functions for all new projects. 1st gen is still supported but receives fewer new runtime versions.
What happens at the deprecation vs decommission date?
Google Cloud Functions uses a two-phase retirement process. At the deprecation date, the runtime is no longer officially supported — you can still deploy functions using it, but you will not receive security patches or bug fixes. At the decommission date (typically 6 months after deprecation), you can no longer deploy new functions or redeploy existing ones on that runtime, and Google may disable functions still running on it. Google provides at least 90 days notice before a runtime is deprecated.
Which runtimes are approaching end of support?
As of early 2026, the runtimes closest to deprecation are: Node.js 20 (deprecated April 2026), Go 1.23 (deprecated February 2026), Ruby 3.2 (deprecated March 2026), and Python 3.10 (deprecated October 2026). Check the deprecation timeline table above for the full list of upcoming dates and recommended upgrade paths.
How do I upgrade my Cloud Function runtime?
To upgrade your runtime, update the --runtime flag in your deployment command (e.g., change --runtime nodejs20 to --runtime nodejs22) or update the runtime field in your cloudfunctions configuration. Test your function locally with the new runtime version first, then deploy to a staging environment. For Cloud Run functions, you can use traffic splitting to gradually shift traffic to the new version. Review the Google Cloud migration guides for any breaking changes between runtime versions.
What are the google-22 and google-24 stacks?
Google Cloud Functions runtimes run on base image stacks that provide the underlying operating system and system libraries. The google-24 stack is based on Ubuntu 24.04 LTS and is used by the newest runtimes. The google-22 stack is based on Ubuntu 22.04 LTS and is the default for most current runtimes. The legacy google-18-full stack (Ubuntu 18.04) is used by older runtimes. Newer stacks receive security updates longer and include more recent system libraries.
Can I use custom container images with Cloud Run functions?
Yes. Cloud Run functions supports deploying from custom container images, giving you full control over the runtime environment, system dependencies, and language versions. Your container must implement the Functions Framework contract for your language. This is particularly useful for languages or versions not yet officially supported, or when you need specific system-level packages. Custom containers are only available with Cloud Run functions (2nd gen), not 1st gen.