Support for deploying your existing apps in the standard 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 standard environment to Cloud Run.

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

Support for TLS version 1.2 and later, along with a corresponding secure set of cipher suites, is in General Availability (GA).

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 standard environment to use TLS version 1.2 and later, along with a corresponding secure set of cipher suites (Preview).

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.

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.

For new projects you create after March 2025, App Engine sets the automatic scaling maximum instances default for standard environment deployments to 20. This change doesn't impact existing apps. To override the default, specify a new max_instances value in your app.yaml file, and deploy a new version or redeploy over an existing version.

Custom organization policies for Serverless VPC Access connectors are now generally available, and can be applied to projects, folders, or organizations.

Node.js 22 is now generally available.

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.

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 Editor role 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 one of the following:

• Grant the Editor role to the App Engine default service account.

• Review the Cloud Build guidance on changes to the default service account and opt out of these changes.

Node.js 22 is now available in preview.

Node.js 10, 12, 14, and 16 have reached end of support on January 30, 2024. Your existing applications using these versions will continue to run and receive traffic. However, App Engine might block re-deployments of applications that use runtimes after their end of support date. We recommend that you upgrade to the latest supported version of Node.js.

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

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

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.

The Node.js 20 runtime for App Engine standard environment is now generally available. Note that Node.js 20 enters long-term support (LTS) in October and is the Node.js "Current" version until that time. We encourage you to explore the new features and benefits included in this release to evaluate their potential impact on your applications. For more information, see the Node.js 20 announcement .

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

The Node.js 20 runtime for App Engine standard environment is now available in preview. Note that Node.js 20 enters long-term support (LTS) in October and is the Node.js "Current" version until that time. We encourage you to explore the new features and benefits included in this release to evaluate their potential impact on your applications. For more information, see the Node.js 20 announcement .

Memory limits for second-generation runtimes have been increased to better support the growing memory utilization of many newer runtimes.

Changes to the default behavior of the Node.js buildpacks are rolling out over the next few days.

For all the services using the Node.js runtime, npm run build now automatically runs during deployment if you have the npm build script defined in your package.json file.

Important: To prevent your build from running the npm run build script, you must either:

• Add a gcp-build script with an empty value in your package.json file: "gcp-build":"". For details about configuring the package.json, see Node.js buildpacks configurations.
• Add the GOOGLE_NODE_RUN_SCRIPTS build environment variable with an empty value such as GOOGLE_NODE_RUN_SCRIPTS="". For details about specifying build environment variables see build_env_variables.

The Node.js runtime now supports the use of Yarn 2 for configuring private modules hosted in Artifact Registry.

The Node.js 18 runtime for App Engine standard environment is now generally available.

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.

You can now use any configured service account in your Cloud project as the app-level default service account, while creating and updating your App Engine applications.

The Node.js 18 runtime for App Engine standard environment is now available in Preview.

Build environment variables support is now generally available.

Specifying a user-managed service account for each App Engine version during deployment is now generally available.

Support for Serverless VPC Access connectors in Shared VPC host projects is now at general availability (GA). Learn about the advantages of this method and how to configure connectors in host projects.

Node.js apps now support private dependencies hosted on an Artifact Registry Node.js package repository. To include private dependencies, list the Artifact Registry repository and configure settings for authenticating with the registry in your .npmrc file.