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 24, 2026
The following runtime language contains important security updates:
- Go 1.24 and later:
1.24.13,1.25.14,1.26.10,1.27.3
The following stacks and their underlying operating system packages have also been updated:
google-22,google-22-fullgoogle-24,google-24-full
Take immediate protective action by rebuilding and redeploying your resources with updated dependencies.
See Security bulletins for Google Cloud for more information.
September 29, 2026
App Engine permanently blocks insecure traffic with TLS version 1.1 and earlier.
For appspot.com domains, this block occurs at the connection level. For custom
domains, the connection might succeed, but the requests are blocked. For more
information, see
Secure minimum TLS.
September 01, 2026
Support for the Go 1.27 runtime is in General Availability (GA).
August 20, 2026
Starting from August 2026, to provide modern security patches and support for MySQL 8.4 and later, the App Engine flexible environment uses Cloud SQL Auth Proxy v2 as the built-in sidecar container for connections to Cloud SQL. To use the latest Cloud SQL Auth Proxy container immediately, restart your VMs or deploy a new version of your application.
August 19, 2026
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.
August 14, 2026
To improve security, starting in August 2026, App Engine opts your application into TLS version 1.2 and later. You can opt out until the end of August 2026. Starting in September 2026, App Engine might permanently block insecure traffic with TLS version 1.1 and earlier. For more information, see Secure minimum TLS.
June 29, 2026
Support for deploying your existing apps in the flexible environment to Cloud Run using
the gcloud beta app migrate-to-run command is in Preview. For more information, see Deploy an App Engine app in the flexible environment to Cloud Run.
March 12, 2026
Support for Go 1.26 runtime is in General Availability.
February 19, 2026
Support for Go 1.26 runtime is in Preview.
October 20, 2025
Support for TLS version 1.2 and later, along with a corresponding secure set of cipher suites, is in General Availability (GA).
August 21, 2025
Support for Go 1.25 runtime is in General Availability (GA).
August 07, 2025
To increase security, starting in March 2025, support for Transport Layer Security (TLS) version 1.1 and earlier is deprecated. Update your application settings in the App Engine flexible environment to use TLS version 1.2 and later, along with a corresponding secure set of cipher suites (Preview).
July 30, 2025
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).
July 15, 2025
Support for Go 1.24 runtime is in Preview.
March 18, 2025
Container Registry is now shut down. We recommend that you use Artifact Registry for storing and managing container images. By default, new deployments created after March 5, 2025, use Artifact Registry instead of Container Registry for storing application build images. For more information, see Migrate App Engine container images to Artifact Registry.
March 03, 2025
Go 1.23 is now generally available.
November 19, 2024
Go 1.23 is now available in preview.
July 30, 2024
In the App Engine page in the Google Cloud console, you can now filter your existing App Engine versions by runtime lifecycle stages. After you apply this filter, the console displays a warning icon for App Engine versions that are approaching end of support, have reached end of support, are deprecated, and are decomissioned.
July 12, 2024
Deployments for new projects might be impacted from the following changes to org policies:
- Starting in May 2024, Google Cloud enforces secure-by-default organization policies for all organization resources. This policy
prevents App Engine from granting the
Editorrole to the App Engine default services accounts by default. - Starting in June 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 versions for the first time may be using the default App Engine service account with insufficient permissions for deploying versions.
If you are impacted by this change, you can do the following:
- Review the Cloud Build guidance on changes to the default service account and opt out of these changes.
- Grant the Editor role to the App Engine default service account.
July 10, 2024
Go version 1.19 and earlier have reached end of support. You cannot re-deploy versions that use runtimes after their end of support date. We recommend that you upgrade your app to use the latest version of Go.
March 26, 2024
Go 1.22 is now generally available.
Starting in Go version 1.22 and later:
- You can't use
go getoutside of a module in the legacyGOPATHmode (GO111MODULE=off). - Go recommends that you use a
go.modfile for managing dependencies.
For more information, see Specify dependencies.
February 26, 2024
December 21, 2023
A warning message now appears before you publish a container image to a public repository.
September 08, 2023
Go 1.21 is now generally available.
August 14, 2023
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.
April 28, 2023
You can now specify version "1.20" in the runtime_version setting of your app.yaml file. Learn more.
May 23, 2022
May 18, 2022
Specifying a user-managed service account for each App Engine version during deployment is now generally available.
July 19, 2021
Specifying a user-managed service account for each App Engine version during deployment is now available in preview. This feature lets you grant different privileges to each version, based on the specific tasks it performs, and avoid granting more privileges than necessary.
June 30, 2021
Requests from internal services to the App Engine flexible environment no longer originate from 10.0.0.1. The IP ranges are as follows:
- Cron requests from newly created or updated App Engine Cron jobs sent to the App Engine flexible environment now come from 0.1.0.2. For Cron jobs created with older gcloud versions (earlier than 326.0.0), Cron requests will come from 0.1.0.1. Previously, these requests only came from both 0.1.0.1 and 10.0.0.1.
- For other Cloud Scheduler jobs and Cloud Tasks queues (including App Engine Task Queues), requests sent to the App Engine flexible environment now only come from 0.1.0.2. Previously, these requests came from both 0.1.0.2 and 10.0.0.1.
- For URL Fetch, requests sent to the App Engine flexible environment now only come from 0.1.0.40. Previously, these requests came from both 0.1.0.40 and 10.0.0.1.
For more information, see Understanding the App Engine firewall.
June 14, 2021
App Engine is now available in the us-west1 (Oregon), asia-southeast1 (Singapore), and asia-east1 (Taiwan) regions.
April 13, 2021
App Engine is now available in the europe-central2 region (Warsaw).
September 25, 2020
You can use network ingress controls so your app only receives requests that are sent from your project's VPC or that are routed through the Cloud Load Balancing load balancer.
July 08, 2020
External HTTP(S) Load Balancing is now supported for App Engine via Serverless network endpoint groups. Notably, this feature allows you to use Cloud CDN with App Engine.
This feature is available in Beta.
March 13, 2020
App Engine is now available in the asia-northeast3 region (Seoul).
March 06, 2020
App Engine is now available in the us-west3 region (Salt Lake City, Utah).
February 11, 2020
App Engine is changing the URLs that you use to send requests to your apps. URLs now include a region ID to help Google route your requests more efficiently and reliably. For example, an app can receive requests at https://PROJECT_ID.REGION_ID.r.appspot.com. This new URL is optional for existing apps and is provided for all new apps.
To ensure a smooth transition, we are slowly updating App Engine to use region IDs. If we haven't updated your Google Cloud project yet, you won't see a region ID for your app. Since the ID is optional for existing apps, you don't need to update URLs or make other changes once the region ID is available for your existing apps.
August 01, 2018
- Support for Go 1.8 on App Engine is now deprecated.
- New Go 1.6 and Go 1.8 app deployments will not be possible from November 1, 2018.
July 10, 2018
- App Engine is now available in the
us-west2region (Los Angeles).
December 14, 2017
Improved access control documentation around deploying apps with IAM roles and service accounts:
October 31, 2017
- App Engine is now available in the
asia-south1region (Mumbai, India).
October 11, 2017
- Announced general availability of App Engine firewall.
October 02, 2017
- For the App Engine flexible environment, all responses are now compressed with gzip by default once you redeploy your app. No changes need to be made to your
app.yamlfile.
March 28, 2017
- The flexible environment is now available in the
europe-westregion.
March 09, 2017
- The .NET core runtime for the App Engine flexible environment is now in Beta.
- The App Engine flexible environment is now generally available (GA). You can run Node.js, Ruby, Python, Java, and Go applications with a 99.95% SLA.
- The PHP 7 runtime for the App Engine flexible environment is now in Beta.
December 06, 2016
- New applications that have not been deployed in the flexible environment must specify
env: truein theapp.yamlfile instead ofvm:true. Applications that were previously deployed can continue to usevm:truebut will need to switch toenv:truein the future. For more details, see upgrade guide.
November 15, 2016
This release includes a few key new features:
- Multi-zonal deployment support.
- A modern networking stack with increased throughput.
- Custom machine types.
- Asia-Northeast1 region availability.
There is a new release of the App Engine flexible environment. To choose this environment, use env:flex instead of vm:true in your app.yaml configuration file. You can learn more about the details of this release by visiting the upgrade guide.
There are also a few breaking changes:
- HTTP headers have been changed.
- Environment variables have been changed.
- There are multiple changes to the
app.yamlschema.
For details and a full list of changes, visit the upgrade guide.
This release also marks the deprecation of a few features:
- The python-compat runtime.
- The python27 runtime.
- The java-compat runtime.
- The jetty9-compat runtime.
- The Go App Engine package no longer works on the App Engine flexible environment. Instead, use the
cloud.google.com/go/...package.
May 02, 2016
- The Ruby runtime is now available for the App Engine flexible environment.