Cloud Functions has been renamed to Cloud Run functions. For more information, see the Cloud Run functions blog post.

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

This page documents production updates to Cloud Run functions. We recommend that Cloud Run functions developers periodically check this list for any new announcements.

You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.

October 10, 2024

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.

September 30, 2024

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

September 23, 2024

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

August 26, 2024

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.

August 21, 2024

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.

July 31, 2024

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

July 11, 2024

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.

June 28, 2024

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

June 27, 2024

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

June 24, 2024

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

June 18, 2024

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.

May 17, 2024

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

March 26, 2024

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

March 06, 2024

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

February 26, 2024

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.

February 12, 2024

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

January 23, 2024

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.

January 15, 2024

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

January 10, 2024

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

January 08, 2024

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

December 21, 2023

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

December 11, 2023

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

December 06, 2023

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

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

November 14, 2023

The ability to optionally configure 2nd gen functions with user-specified concurrency and vCPU is now available at the General Availability release level.

November 08, 2023

Cloud Functions now supports on-deployment security updates (1st gen and 2nd gen) and fully automatic security updates (1st gen only). For details, see Execution environment security.

November 06, 2023

Cloud Functions now supports the Python 3.12 runtime at the General Availability release level.

October 16, 2023

Cloud Functions now supports the Python 3.12 runtime at the Preview release level.

October 11, 2023

Cloud Functions (2nd gen) now supports Shared VPC ingress at the General Availability release level. Shared VPC traffic is now considered "internal" for functions that are connected to the Shared VPC network.

September 07, 2023

Cloud Functions now supports the Go 1.21 runtime at the General Availability release level.

August 29, 2023

Cloud Functions (2nd gen) is now the default choice in the Google Cloud console user interface.

August 16, 2023

Cloud Functions now supports pre-deployment testing in the Google Cloud console at the Preview release level.

August 14, 2023

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

August 07, 2023

Accessing a service that's prohibited by the Internal or Internal and Cloud Load Balancing ingress setting now results in a 404 rather than 403 error code.

July 31, 2023

The following new regions are now available: europe-southwest1, europe-west8, europe-west9, us-south1, and us-east5. See Locations for details.

June 27, 2023

Cloud Functions now supports performance recommendations that analyze cold starts and suggest setting up minimum instances to improve function performance at the General Availability release level.

June 26, 2023

The Node.js 20 runtime is now available for Google Cloud Functions at the GA release level. Note that Node.js 20 will enter long-term support (LTS) in October and is the Node.js "Current" release until then. The Node.js community encourages you to explore the new features and benefits included in this release. For more information, see the Node.js 20 announcement.

June 23, 2023

The Java runtime now supports projects that use Maven wrappers.

June 16, 2023

Cloud Functions 2nd gen now supports deterministic URLs (similar to 1st gen), at the General Availability release level. This change will not just affect new 2nd gen functions. Previously deployed 2nd gen functions will be retroactively assigned a deterministic cloudfunctions.net URL. The function's previous run.app URL will continue to work also. If your 2nd gen function was last deployed before June 15th, 2023, be sure to redeploy it before using cloudfunctions.net URL as an auth token audience.

June 14, 2023

Cloud Functions now supports customer-managed encryption keys for 2nd gen functions at the General Availability release level.

June 09, 2023

You can now create and then configure Serverless VPC Access connector for your function directly from the Create form in the Google Cloud console at the Preview release level.

June 01, 2023

You can use the Pnpm package manager to configure dependencies for Node.js runtimes. Learn how to configure your runtime.

May 16, 2023

You can now restrict new deployments by product generation (1st gen or 2nd gen). This feature is at the General Availability release level.

May 15, 2023

Cloud Functions has added support for a new runtime, PHP 8.2, at the General Availability release level. PHP 8.2 adds significant new functionality over PHP 8.1 and uses Ubuntu 22.04 for its base O/S image.

Cloud Functions now supports 2nd gen Firestore triggers through Eventarc at the Preview release level.

May 08, 2023

Cloud Functions now supports the Node.js 20 runtime at the Preview release level.

April 20, 2023

There is a change in retry policy for 1st gen functions that use Pub/Sub subscriptions. Newly created 1st gen functions with "retry on failure" enabled will now use exponential backoff, configured with a minimum backoff of 10 seconds and a maximum backoff of 600 seconds. This new policy replaces the old "retry immediately" policy. This policy is applied to new 1st gen functions the first time you deploy them. It is not retroactively applied to existing functions, even if you redeploy them. 2nd gen functions will continue to use an exponential backoff strategy. For details, see Retrying event-driven functions.

April 18, 2023

Cloud Functions (2nd gen) has added support at the Preview release level for accepting requests from the Shared VPC network that a function is connected to, including when Ingress is configured as "Internal" or "Internal and Cloud Load Balancing."

April 11, 2023

All 1st and 2nd gen Google Cloud Functions using the Node.js runtime now automatically run the npm run build command during deployment if they define an npm build script in their package.json file. This feature is rolling out over the next few days.

Important: If you prefer to prevent your build from running the npm run build script, you can either:

Add a gcp-build script with an empty value in your package.json file: "gcp-build":""
Set the environment variable GOOGLE_NODE_RUN_SCRIPTS to the empty string to prevent all scripts from running -- for example, by including the --set-build-env-vars=GOOGLE_NODE_RUN_SCRIPTS="" option with your gcloud functions deploy command.

For details about configuring package.json, see Node.js buildpack configuration. For details about setting environment variables see setting environment variables.

April 06, 2023

Cloud Functions now supports the use of the Yarn 2 package manager with private Node.js modules.

April 04, 2023

You can now use uppercase letters and underscores in the function name you specify for a 2nd gen function when you deploy the function.

April 03, 2023

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

March 27, 2023

Cloud Functions has added support for a new runtime, Go 1.20, at the General Availability release level.

March 17, 2023

Cloud Functions has added support for customer-managed encryption keys for 2nd gen functions at the Preview release level.

February 28, 2023

Cloud Functions now supports the Python 3.11 runtime at the General Availability release level.

February 27, 2023

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

New performance recommendations are supported for Cloud Functions, which analyze cold starts and suggest setting up minimum instances to improve function performance. At the Preview release level.

February 13, 2023

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

January 30, 2023

We've added support dates for language runtimes that have reached end of support from their open source communities. Please refer to the Runtimes Support Schedule for future updates to runtime languages

January 18, 2023

The ability to optionally configure 2nd gen functions with user-specified concurrency and vCPU is now available in preview.

Cloud Functions now supports the Node.js 18 runtime at the General Availability release level.

January 10, 2023

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

January 06, 2023

Cloud Functions now supports the following runtimes at the General Availability release level.

December 21, 2022

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

December 13, 2022

The cloudfunctions.googleapis.com/v2 API now supports reading 1st gen functions, using the get and list methods. Function responses contain an Environment field that differentiates between 1st and 2nd gen functions.

You can use the filter field to restrict the response to only 2nd gen functions, for example: filter=environment="GEN_2".

Note that 1st gen functions in europe-west5 can't be read from the v2 API as the region is not available yet in 2nd gen.

If you are using an older version of gcloud, the gcloud functions list command may show 1st gen functions twice. Updating to a newer version of gcloud should fix this.

November 22, 2022

Cloud Functions has added support for a new runtime, Node.js 18, at the Preview release level.

November 14, 2022

Cloud Functions container runtimes have been patched against CVE-2022-3786 and CVE-2022-3602. Affected runtime languages are:

Java 17
Python 3.10
Go 1.18/1.19
.NET 6

You should redeploy functions using the affected runtime languages as soon as possible. Google does not automatically update the base image in use for already-deployed functions. Google will automatically apply the most updated runtime version to the redeployed function.

November 08, 2022

Cloud Functions has added support for the following new runtimes at the Preview release level:

October 24, 2022

Cloud Functions now supports the .NET Core 6.0 runtime at the General Availability release level.

September 12, 2022

Cloud Functions has added support for a new runtime, .NET Core 6.0, at the Preview release level.

August 03, 2022

Cloud Functions has released Cloud Functions (2nd gen), available at the General Availability release level. Cloud Functions (2nd gen) is Google Cloud's next-generation Functions-as-a-Service offering. This new version of Cloud Functions comes with an advanced feature set, giving you more powerful infrastructure, advanced control over performance and scalability, more control around the functions runtime, and triggers from over 90 event sources.

See Cloud Functions version comparison for details.

July 06, 2022

Cloud Functions (1st gen) now supports Google-managed Artifact Registry at the General Availability release level.

Cloud Functions now supports the following runtimes at the General Availability release level:

July 01, 2022

Cloud Functions now supports PHP 8.1 at the General Availability release level.

June 30, 2022

Cloud Functions now supports Python 3.10 at the General Availability release level.

June 27, 2022

Cloud Functions now supports Java 17 at the General Availability release level.

June 14, 2022

The Python 3.10 runtime (preview) now uses Ubuntu 22.

June 06, 2022

The Java 17 runtime (preview) now uses Ubuntu 22.

May 25, 2022

We have updated the documentation to clarify that to get the updates and security patches for runtimes and their dependencies, you need to deploy a function. Security patches are not applied otherwise.

May 04, 2022

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

May 03, 2022

Cloud Functions has added support for the following new runtimes at the Preview release level:

April 01, 2022

Cloud Functions (1st gen) has added support for Google-managed Artifact Registry at the Preview release level.

March 31, 2022

Cloud Functions (1st gen) support for customer-managed encryption keys (CMEK) is now at the General Availability release level.

March 24, 2022

Support for Serverless VPC Access connectors in Shared VPC host projects is now at the General Availability release level. Learn about the advantages of this method and how to configure connectors in host projects.

March 21, 2022

Support for Firebase Remote Config, Firebase Alerts, and Firebase Test Lab triggers is now in Preview. This only applies to Cloud Functions (2nd gen).

March 14, 2022

Cloud Functions has added support for the following new runtimes at the Preview release level:

March 07, 2022

Added Terraform support for Cloud Functions (2nd gen).

February 16, 2022

Cloud Functions has added support for low-configuration access to private dependencies on Artifact Registry in in Node.js and Python.

February 14, 2022

Cloud Functions has released Cloud Functions (2nd gen), available at the Preview release level. Cloud Functions (2nd gen) is Google Cloud's next-generation Functions-as-a-Service offering. This new version of Cloud Functions comes with an advanced feature set, giving you more powerful infrastructure, advanced control over performance and scalability, more control around the functions runtime, and triggers from over 90 event sources.

See the Cloud Functions (2nd gen) documentation for details.

January 25, 2022

Cloud Functions support for secrets is now at the General Availability release level.

December 08, 2021

Cloud Functions has added support for customer-managed encryption keys, available at the Preview release level.

December 07, 2021

Cloud Functions support for setting a minimum number of instances is now at the General Availability release level.

December 02, 2021

Internal ingress from Workflows to Cloud Functions is now at the General Availability release level.

November 22, 2021

Cloud Functions is now available in the following region:

us-west1 (Oregon)

See Cloud Functions Locations for details.

November 17, 2021

Cloud Functions now supports the following runtimes at the General Availability release level:

September 15, 2021

Cloud Functions now supports PHP 7.4 at the General Availability release level.

September 09, 2021

Firestore triggers for Cloud Functions are now supported at the General Availability release level.

September 03, 2021

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

August 30, 2021

Cloud Functions adds support for setting a minimum number of instances, available at the Preview release level. For more information, see the blog post.

August 26, 2021

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

August 24, 2021

Cloud Functions offers a native integration with Secret Manager, available at the Preview release level. For more information, see the blog post.

August 10, 2021

The use of private worker pools is now available for building your functions.

July 07, 2021

Cloud Functions now logs pending queue requests abort error messages.

July 02, 2021

Cloud Functions now supports .NET at the General Availability release level. This runtime is based on .NET Core 3.1.

June 28, 2021

Cloud Functions is now available in the following region:

asia-east1 (Taiwan)

See Cloud Functions Locations for details.

June 14, 2021

Cloud Functions is now available in the following region:

asia-southeast1 (Singapore)

See Cloud Functions Locations for details.

June 07, 2021

Cloud Functions now supports Ruby 2.6 and 2.7 at the General Availability release level.

April 19, 2021

Cloud Functions has added support for a new runtime, PHP 7.4, in Preview.

Cloud Functions now supports the following runtimes at the General Availability release level:

April 12, 2021

Cloud Functions is now available in the following region:

europe-central2 (Warsaw)

See Cloud Functions Locations for details.

March 18, 2021

Shared VPC on Cloud Functions is now at general availability (GA).

February 04, 2021

There is now a security level feature for HTTP functions that controls whether the function's URL supports HTTPS only, or both HTTP and HTTPS.

January 13, 2021

Cloud Functions has added support for a new runtime, Node 14, in Preview.

Cloud Functions has added support for a new runtime, Python 3.9, in Preview.

January 11, 2021

Cloud Functions has added support for a new runtime, Ruby, in Preview. This runtime supports Ruby 2.6 and Ruby 2.7.

November 19, 2020

Cloud Functions has added support for a new runtime, .NET, in Preview. This runtime is based on .NET Core 3.1.

November 16, 2020

Cloud Functions now supports Node.js 12 at the General Availability release level.

November 11, 2020

Cloud Functions now supports Python 3.8 at the General Availability release level.

October 13, 2020

In runtimes that use buildpacks you can now configure aspects of your build by setting build configuration variables. See Using Environment Variables for more information. In Preview.

August 26, 2020

Cloud Functions Node 10 runtime now builds container images in the user's project, providing direct access to build logs and removing the preset build-time quota.

August 14, 2020

Cloud Functions now supports Java 11 at the General Availability release level.

August 05, 2020

Cloud Functions Java 11, Python 3.7 or 3.8, and Go 1.13 runtimes now build container images in the user's project, providing direct access to build logs and removing the preset build-time quota.

See Building Cloud Functions for details.

The Go 1.11 runtime is deprecated as of 2020-08-05. To ensure that your functions are on a supported version of Go, migrate them to Go 1.13. For more discussion of Cloud Functions runtime support policy, see Runtime Support.

July 31, 2020

Cloud Functions is now available in the following regions:

asia-south1 (Mumbai)
asia-southeast2 (Jakarta)
asia-northeast3 (Seoul)

See Cloud Functions Locations for details.

July 23, 2020

Serverless VPC Access support for Shared VPC is now available in Beta.

July 15, 2020

Cloud Functions has added support for a new runtime, Node 12, in Beta.

Cloud Functions has added support for a new runtime, Python 3.8, in Beta.

July 10, 2020

Cloud Functions is now available in the following regions:

us-west2 (Los Angeles)
us-west4
southamerica-east1 (Sao Paulo)
asia-northeast2 (Osaka)

See Cloud Functions Locations for details.

July 07, 2020

External HTTP(S) Load Balancing is now supported for Google Cloud Functions via Serverless network endpoint groups.

Notably, this feature allows you to use Cloud CDN and Cloud Armor with Google Cloud Functions.

This feature is available in Beta.

June 19, 2020

Cloud Functions is now available in the following regions:

australia-southeast1 (Sydney)
northamerica-northeast1 (Montreal)

See Cloud Functions Locations for details.

June 12, 2020

Cloud Functions is now available in the following regions:

europe-west6 (Zurich)
us-west3 (Salt Lake City)

See Cloud Functions Locations for details.

June 05, 2020

The Node.js 8 runtime is deprecated as of 2020-06-05. To ensure that your functions are on a supported version of Node.js, migrate them to Node.js 10.

For more discussion of Cloud Functions runtime support policy, see Runtime Support.

May 28, 2020

Cloud Functions now supports Go 1.13 at the General Availability release level.

May 26, 2020

Cloud Functions has added support for a new runtime, Java 11, in Beta:

The Java Runtime

May 18, 2020

Cloud Functions now supports Node.js 10 at the General Availability release level.

March 31, 2020

Cloud Functions now supports Connecting to Cloud SQL at the General Availability release level.

The Beta release introduced improved security when accessing Cloud SQL from functions via the /cloudsql filesystem path. Most functions have been automatically upgraded. In some cases, you may see warning messages in Stackdriver logging to help you complete the required upgrade steps.

March 24, 2020

Cloud Functions now supports network settings at the General Availability release level.

Cloud Functions now supports VPC Service Controls at the General Availability release level.

February 13, 2020

HTTP functions now require authentication by default. See Managing Access via IAM for details.

January 31, 2020

Cloud Functions has added the network settings feature at the Beta release level. Network settings enable you to control network ingress and egress on individual functions.

Cloud Functions now supports VPC Service Controls at the Beta release level. VPC Service Controls is a feature that allows you to set up a secure perimeter to guard against data exfiltration.

January 29, 2020

Cloud Functions is now available in the following region:

europe-west3 (Frankfurt)

See Cloud Functions Locations for details.

January 14, 2020

Cloud Functions has added support for a new runtime, Go 1.13, in Beta:

The Go Runtime

December 11, 2019

Cloud Functions now supports Serverless VPC Access at the General Availability release level.

November 26, 2019

The ListFunctions API method now handles unreachable locations when the specified location is "-" to list functions across all locations. Previously, if one or more locations were unreachable, the entire ListFunctions request would fail. Now the request will return functions from all reachable locations along with an "unreachable" field containing a list of location names that did not respond successfully. Learn more about working with unreachable resources.

November 12, 2019

Cloud Functions now supports IAM policies to control access to HTTP functions at the General Availability release level.

October 14, 2019

The max instances feature is now at the General Availability release level:

Controlling Scaling Behavior
Note that when you have set a max instances limit, you may encounter a scenario where there are insufficient instances to meet incoming traffic load. Requests that time out due to unavailability of instances send a 429 response.

July 01, 2019

Cloud Functions is now available in the following region:

us-east4 (Northern Virginia)

See Cloud Functions Locations for details.

June 26, 2019

Cloud Functions now supports IAM policies to control access to HTTP functions in beta. During beta, functions will be deployed publicly and you can restrict access by setting IAM policies.

June 06, 2019

With the end-of-life of Node 6, the Cloud Functions Local Emulator tool for Google Cloud Functions for Node 6 is no longer being maintained and is marked as deprecated. Use the Functions Framework to run a function locally.

April 19, 2019

Completed rollout of update to the Go Cloud Functions runtime. Go has been updated from version 1.11.5 to 1.11.6. All function deployments should get this version automatically.

April 18, 2019

The Node.js 6 runtime is deprecated as of 2019-04-18. On 2019-04-30, Node.js 6 will reach its end-of-life and will no longer receive updates from the Node.js maintainers. To ensure that your functions are on a supported version of Node.js, migrate them to Node.js 8 or Node.js 10. After 2020-04-22, function deployments that use Node.js 6 will be blocked. Cloud Functions that continue to use Node.js 6 after this time may be disabled.

For more discussion of Cloud Functions runtime support policy, see Runtime Support.

April 09, 2019

Cloud Functions now supports Serverless VPC Access, which is available at the Beta release level. This feature enables your functions to connect to internal resources in your VPC network, such as Compute Engine VM instances, Cloud Memorystore for Redis instances, and more.

April 04, 2019

Now when you deploy a function for the first time using the gcloud command-line tool or the API, you must specify your function's runtime explicitly. If you are using gcloud, include the --runtime flag. If you are using the API, set the runtime field when creating a CloudFunction. You do not need to specify the runtime on subsequent function deployments.

April 03, 2019

Cloud Functions has added support for a new runtime, Node.js 10, in Beta:

The Node.js 10 Runtime

April 01, 2019

Made the following changes:

The following runtimes are now at the General Availability release level:
Node.js 8 runtime
Python 3.7 runtime
Go 1.11 runtime

Cloud Functions is now available in 2 new regions. See Cloud Functions Locations for details:
europe-west2 (London)
asia-east2 (Hong Kong)

March 29, 2019

Completed rollout of update to the Go Cloud Functions runtime. Go has been updated from version 1.11 to 1.11.5. All function deployments should get this version automatically.

March 28, 2019

The max instances feature is now at Beta Availability release level. This feature allows you to limit the degree to which your function scales up in response to inbound request load.

March 22, 2019

Fixed an issue where events would no longer be delivered to a background function if the function hadn't been triggered at least once in the last 30 days. This fix will be automatically applied to any new functions. The fix will be applied to existing functions upon re-deployment.

February 27, 2019

Made the following changes:

The default function calls quota has been raised to 40,000,000 in all regions.

The requests package installed for Python functions was upgraded from 2.19.1 to 2.21.0.

February 20, 2019

Completed rollout of update to the Node.js 6 Cloud Functions runtime. Node.js 6 has been updated from version 6.14.0 to 6.16.0.

February 14, 2019

Fixed an issue where functions would, under some circumstances, be triggered multiple times when a single event was delivered. Note that event delivery follows an at least once guarantee, which means that, rarely, event re-delivery can occur.

February 06, 2019

Completed rollout of update to the Node.js 8 Cloud Functions runtime. Node.js 8 has been updated from version 8.14.0 to 8.15.0.

Started rolling out an update of the Node.js 6 runtime to version 6.16.0. Node.js 6 functions deployed after February 4, 2019 may start to receive the updated version.

January 16, 2019

Cloud Functions has added support for a new runtime, Go, in Beta:

The Go Runtime

January 15, 2019

Started rolling out an update of the Node.js 8 runtime to version 8.15.0. Node.js 8 functions deployed after January 14, 2019 might start to use the updated version.

December 20, 2018

Completed rollout of update to the Node.js 8 Cloud Functions runtime. Node.js 8 has been updated from version 8.11.1 to 8.14.0. The update of Node.js 6 from version 6.14.0 to 6.15.0 has been rolled back. Node.js 6 is still at 6.14.0, and now won't be updated until January 2019.

December 17, 2018

Started a gradual rollout of updates to the Node.js 6 and Node.js 8 Cloud Functions runtimes. Node.js 6 will be updated from version 6.14.0 to 6.15.0. Node.js 8 will be updated from version 8.11.1 to 8.14.0. We will update the status in the release notes when the rollout has completed.

December 04, 2018

The environment variables feature is now at the General Availability release level:

Using Environment Variables

November 06, 2018

The Google Cloud Functions Python runtime has been updated to version 3.7.1.

July 24, 2018

Cloud Functions is now at the General Availability release level and is recommended for production loads. This release includes:

Support for new runtimes: Node.js 8 and Python, in Beta.

The Cloud Functions gcloud commands are now at the General Availability release level. The beta label is no longer required (unless you are deploying a function written in Node.js 8 or Python, which are Beta features).

July 12, 2018

Launched the environment variables feature to open beta:

Using Environment Variables

June 21, 2018

Added documentation describing how to connect to Cloud SQL:

Connecting to Cloud SQL

June 20, 2018

Cloud Functions is now available in the following regions:

us-central1 (Iowa)
us-east1 (South Carolina)
europe-west1 (Belgium)
asia-northeast1 (Tokyo)

See Cloud Functions Locations for details.

June 07, 2018

The v1beta2 version of the Cloud Functions API was part of our Beta launch. New users should use the v1 API, and existing users should migrate to the v1 API.

May 15, 2018

Google Cloud Functions Node.js runtime updated to v6.14.0.

February 09, 2018

Introduced a set of more powerful, finer-grained trigger types for Cloud Storage and changed the format for Cloud Storage and Cloud Pub/Sub events. For details, see Google Cloud Storage Triggers and Google Cloud Pub/Sub Triggers.

Added documentation describing best practices for testing and deploying Cloud Functions: