Cloud Run functions (formerly known as Cloud Functions) release notes

Support for the Go 1.27 runtime is in General Availability (GA).

Support for the Go 1.27 runtime is in Preview.

Starting from Go runtime version 1.26 and later, the lifecycle support dates align more closely with the Go community release cycle. For more information, see Runtime support schedule.

The Cloud Run functions upgrade tool is in General Availability. Use this tool to upgrade 1st gen functions to Cloud Run functions.

Support for the Node.js 26 runtime is in Preview.

Support for Ruby 4.0 runtime is in General Availability.

Support for Go 1.26 runtime is in General Availability.

Support for Ruby 4.0 runtime is in Preview.

Support for PHP 8.5 runtime is in General Availability.

Support for the ability to configure Direct VPC egress for 2nd gen functions is in General Availability.

Support for Go 1.26 runtime is in Preview.

Support for .NET 10 runtime is in General Availability.

Support for PHP 8.5 runtime is in Preview.

Support for .NET 10 runtime is in Preview.

You can now configure Direct VPC egress for 2nd gen functions. This support is at the Preview release level.

Support for Java 25 runtime is in General Availability.

Support for Python 3.14 runtime is in General Availability. Starting from Python version 3.14 and later, the Python Buildpack uses the uv package manager as the default installer for the dependencies you specify in your requirements.txt file. You can also use pip as the default installer for these versions by setting the GOOGLE_PYTHON_PACKAGE_MANAGER environment variable to pip. For more information, see Specify dependencies in Python.

Support for Node.js 24 runtime is in General Availability.

Support for Python 3.14 runtime is in Preview. Starting from Python version 3.14 and later, the Python Buildpack uses the uv package manager as the default installer for the dependencies you specify in your requirements.txt file. You can also use pip as the default installer for these versions by setting the GOOGLE_PYTHON_PACKAGE_MANAGER environment variable to pip. For more information, see Specify dependencies in Python.

Support for Java 25 runtime is in Preview.

Cloud Run functions (1st gen) supports the Node.js 22 runtime at the General Availability release level.

Cloud Run functions now provides an upgrade tool for upgrading 1st gen functions to Cloud Run. This feature is in Preview.

Support for Go 1.25 runtime is in General Availability (GA).

Support for Go 1.25 runtime is in Preview. This runtime is available for early testers using existing release candidates.

Support for Go 1.24 runtime is in General Availability (GA).

Support for Node.js 24 runtime is in Preview. Node.js 24 is in the Current release state and enters long-term support (LTS) in October 2025. For more information, see Node.js v24.0.0 (Current) in the Node.js website.

Support for the Go 1.24 runtime is in Preview.

Support for the PHP 8.4 runtime is in General Availability (GA).

Support for the Ruby 3.4 runtime is in General Availability (GA).

For Java functions that use functions-framework version 1.4.0 or later, you can now use the logging class java.util.logging.Logger to add a unique execution ID to log outputs.

Labels you previously set for your Cloud Run functions using either gcloud functions commands or the Cloud Functions v2 API propagate to Cloud Run when you deploy your functions in Cloud Run. For more information on creating labels in Cloud Run, see Configure labels for services.

Support for the Ruby 3.4 runtime is in Preview.

Support for the PHP 8.4 runtime is in Preview.

Support for the Python 3.13 runtime is in General Availability (GA).

Cloud Run functions now supports the Python 3.13 runtime at the Preview release level.

Cloud Run functions now supports the Go 1.23 runtime at the General Availability release level.

Support for deploying v2 functions in Cloud Run is now in general availability (GA). This lets you customize your function as you would a Cloud Run service. This change removes support for creating, deploying, or updating v2 functions in the Google Cloud console. However, you can still manage functions created with the Cloud Functions v2 API using the Cloud Functions gcloud CLI, the Cloud Functions v2 API, or the Cloud Run Cloud Console. See Cloud Run functions comparison for more details.

Cloud Run functions created with the Cloud Functions (v2) API (cloudfunctions.googleapis.com) can now be detached so that they can only be managed through the Cloud Run Admin API (run.googleapis.com). When the detach operation completes, your function will retain its cloudfunctions.net URLs and triggers, and can only be managed using the Cloud Run Admin API. Note that the detach operation is irreversible. For more information see Manage functions.

You can now create custom organization policies for Serverless VPC Access connectors and apply them to projects, folders, or organizations. This support is at the General Availability release level.

Cloud Run functions now supports the Go 1.23 runtime at the Preview release level.

Cloud Run functions now supports the Node.js 22 runtime at the General Availability release level.

You can now manage function resources using custom constraints that get enforced at the project level. This support is at the General Availability release level.

You can now manage function resources using custom constraints that get enforced at the project level. This support is at the Preview release level.

The runtime support schedule for some PHP runtimes has been extended to match PHP's public support schedule.

The Cloud Run functions (cloud functions v2 API) build process now supports cross-project Artifact Registry repositories for greater configurability. This support is at the Preview release level.

Cloud Functions has been renamed to Cloud Run functions.

• Cloud Functions (1st gen) is now known as Cloud Run functions (1st gen).
• Cloud Functions (2nd gen) is now known as Cloud Run functions.

Learn more in the blog post.

You can also deploy new functions, and modify existing functions that were created with the Cloud Functions v2 API in Cloud Run. This enables you to customize your function as you would a Cloud Run service.

Cloud Functions now supports the Ruby 3.3 runtime at the General Availability release level.

Starting in July 2024, Cloud Build has changed the default behavior for how Cloud Build uses service accounts in new projects. This change is detailed in Cloud Build Service Account Change. As a result of this change, new projects deploying functions for the first time may be using a default Cloud Build service account with insufficient permissions for building a function. If you are impacted by this change you can do one of the following:

• Review the Cloud Build guidance on changes to the default service account and opt out of these changes.
• Add the Cloud Build Service Account role (roles/cloudbuild.builds.builder) to the default Compute Service Account.
• Create a custom build service account for function deployments.

Cloud Functions 1st gen and 2nd gen now support custom service accounts for Cloud Build at the General Availability release level.

To simplify searches and improve your documentation experience, we have split the 1st generation and 2nd generation documentation into separate documentation sets.

Cloud Functions (2nd gen) now supports fully automatic security updates. For details, see the document Execution environment security.

Cloud Functions has added support for a new runtime, Ruby 3.3, at the Preview release level.

You can now enable execution ID in the logs for 2nd gen Python functions that use functions-framework >= 3.7.0 and 2nd gen Node.js functions that use functions-framework >= 3.4.0 by setting the runtime environment variable LOG_EXECUTION_ID to true.

Cloud Functions (2nd gen) now supports the Node.js 22 runtime at the Preview release level.

Cloud Functions (2nd gen) now supports the Go 1.22 runtime at the General Availability release level.

Cloud Functions (1st gen) now supports custom service accounts for Cloud Build, at the Preview release level.

Cloud Functions now supports the PHP 8.3 and Java 21 runtimes at the General Availability release level for 2nd gen functions.

Cloud Functions now supports the Go 1.22 runtime at the Preview release level.

Cloud Functions now supports the PHP 8.3 runtime at the Preview release level for 2nd gen functions.

The option to update a Serverless VPC Access connector is now available at the General Availability release level. This feature allows you to edit the machine (instance) type, as well as the minimum and maximum number of instances.

Cloud Functions (1st gen) now uses Artifact Registry as the default container registry. See Customize the Cloud Functions build process for details.

Cloud Functions now supports the .NET 8 runtime at the General Availability release level for 2nd gen functions.

Cloud Functions (2nd gen) now supports custom service accounts for Cloud Build, at the Preview release level.

A warning message now appears before you publish a container image to a public repository.

The new region me-west1 is now available. See Locations for details.

Cloud Functions (2nd gen) now supports the .NET 8 runtime at the Preview release level.

Cloud Functions (2nd gen) now supports the Java 21 runtime at the