Runtimes on Cloud Run are base images that include components and operating system, software required to build and execute code written for a specific programming language, and software to support your function.
Google provides support for a runtime during General availability (GA) . During this support window:
- Runtime components are regularly updated with security and bug fixes.
- To maintain stability, Cloud Run avoids implementing breaking features or breaking changes into the runtime. Breaking changes will be announced in advance in Cloud Run release notes .
When a language version is no longer actively maintained by the respective community, Cloud Run will also stop providing maintenance and support for that language runtime. Before a runtime reaches the deprecation phase as described in the runtimes support schedule , Google will provide a notification to customers in the Google Cloud console.
Google may make changes to any runtime's support schedule or lifecycle in accordance with the terms of your agreement for the use of Google Cloud services.
Runtime lifecycle
| GA-level support | Deprecated | Decommissioned | |
|---|---|---|---|
|
Creation and redeployment
|
Yes | Yes | No |
|
Running existing workloads
|
Yes | Yes | May be disabled |
|
Language patches
|
As per policy | As per policy | No updates |
|
Patching system packages
|
As per policy | As per policy | No updates |
|
Patching OS
|
As per policy | As per policy | No updates |
|
Customer support
|
GA-level support | No runtime support | No runtime support |
Notification Period
Cloud Run will begin issuing notifications 90 days before the runtime reaches deprecation. Upon notification, you should prepare to upgrade your function to a newer supported runtime .
Deprecation and Decommissioning
When a component is no longer actively maintained, Cloud Run may deprecate and eventually remove the runtime.
This has three aspects: a publication of the deprecation date, a deprecation period, and a decommission date. In the following schedule , the deprecation date is the start of the deprecation period and ends at the beginning of the decommission date. The decommission date indicates the start of the decommission period.
During the deprecation period, you can generally continue to create new workloads and update existing workloads using the runtime. You should use this time to migrate workloads that use the deprecated runtime to a more up-to-date runtime.
After the decommission date, you can no longer create new workloads or update existing workloads using the runtime. You must choose a more up-to-date runtime to deploy your workloads. Workloads that continue to use a decommissioned runtime may be disabled.
Support Schedule
Here is the list of supported Cloud Run runtimes, as well as runtimes that have been deprecated or decommissioned.
Based on qualification and stability of releases, availability and key dates might be delayed. A blank deprecation or decommission date means that phase has not yet been scheduled. Revisit this page to stay up to date.
Node.js
(Preview only)
Python
Go
Java
Ruby
PHP
| Runtime | Runtime ID | Stacks | Runtime base image | Deprecation | Decommission |
|---|---|---|---|---|---|
|
PHP 8.4
|
php84 | google-22-full (default) | google-22-full/php84 | 2028-12-31 | 2029-06-30 |
|
PHP 8.3
|
php83 | google-22-full (default) | google-22-full/php83 | 2027-12-31 | 2028-06-30 |
|
PHP 8.2
|
php82 | google-22-full (default) | google-22-full/php82 | 2026-12-31 | 2027-06-30 |
|
PHP 8.1
|
php81 | google-18-full | google-18-full/php81 | 2025-12-31 | 2026-06-30 |
|
PHP 7.4
|
php74 | google-18-full | google-18-full/php74 | 2024-01-30 | 2025-01-30 |
