App Engine standard environment for Ruby release notes

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.

December 09, 2024

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

July 31, 2024

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 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.

June 18, 2024

Ruby 3.3 is now available in preview.

January 30, 2024

Ruby 2.5, 2.6, and 2.7 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 Ruby.

January 23, 2024

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.

December 21, 2023

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

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.

May 01, 2023

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

April 14, 2023

The Ruby 3.2 runtime for App Engine standard environment is now generally available.

March 06, 2023

The Ruby 3.2 runtime for App Engine standard environment is now available in preview.

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

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.

November 01, 2022

Build environment variables support is now generally available.

May 18, 2022

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

May 04, 2022

The Ruby 3.0 runtime for App Engine standard environment is now generally available.

March 24, 2022

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.

March 14, 2022

January 28, 2022

Builds are now handled by regional Cloud Build pools within the selected App Engine region. To view build logs, go to Cloud Build in the Cloud Console, select the History page, and select the region you would like to filter by.

November 03, 2021

Egress settings for Serverless VPC Access are now generally available. Egress settings allow you to specify whether or not to send traffic with external destinations through your Serverless VPC Access connector, which is necessary if you want to set up a static outbound IP address for your App Engine service.

July 21, 2021

Egress settings are now available for Serverless VPC Access. Egress settings allow you to specify whether or not to send traffic with external destinations through your Serverless VPC Access connector, which is necessary if you want to set up a static outbound IP address for your App Engine service.

June 30, 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.

Requests from newly created or updated App Engine Cron jobs sent to the App Engine standard 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 0.1.0.1. See Understanding the App Engine firewall for more information.

June 14, 2021

App Engine is now available in the us-west1 (Oregon), asia-southeast1 (Singapore), and asia-east1 (Taiwan) regions.

April 27, 2021

Automatic scaling elements min_instances and min_idle_instances will now only apply to versions of a service that have been configured to receive traffic. This change is to reduce unexpected billing due to instances running old versions that are not intended to receive traffic.

April 20, 2021

Build environment variables support is now available in preview.

April 14, 2021

Serverless VPC Access support for Shared VPC is now generally available.

April 13, 2021

App Engine is now available in the europe-central2 region (Warsaw).

March 26, 2021

App Engine standard environment provides a new metric, CPU Utilization, which indicates the CPU utilization average over all active instances. For more information, see Google Cloud metrics.

November 18, 2020

The Ruby 2.6 and 2.7 runtimes for the App Engine standard environment are now generally available.

November 12, 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. This feature is now generally available.

September 25, 2020

If you use Cloud Load Balancing, you can use network ingress controls so your app only receives requests that are routed through the load balancer.

July 23, 2020

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.

July 06, 2020

The Ruby 2.6 and 2.7 runtime Betas for the App Engine standard environment are now available.

June 08, 2020

App Engine is now available in the asia-southeast2 region (Jakarta).

May 14, 2020

To get a fine-grained view of billing data for each resource used by your App Engine services, you can apply labels to the services, export your billing data to BigQuery, and run queries. For more information, see Labeling App Engine resources.

April 20, 2020

App Engine is now available in the us-west4 region (Las Vegas, NV).

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://<var>PROJECT_ID</var>.<var>REGION_ID</var>.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.

February 06, 2020

  • You can no longer apply new spending limits to projects. Existing spending limits will continue to work. For more information on how you can limit app costs, see Limiting Costs.

December 11, 2019

July 30, 2019

  • The AppCfg tooling and the legacy standalone App Engine SDK, delivered through the GoogleAppEngineLauncher.dmg, GoogleAppEngine.msi, and google_appengine.zip files, are now deprecated. Google will shut down and remove support on July 30, 2020.

June 12, 2019

  • The Ruby runtime for the App Engine standard environment is now Beta.

April 18, 2019

  • App Engine is now available in the asia-northeast2 region (Osaka, Japan).

April 15, 2019

  • App Engine is now available in the europe-west6 region (Zürich, Switzerland).

October 22, 2018

  • App Engine is now available in the asia-east2 region (Hong Kong).

July 10, 2018

  • App Engine is now available in the us-west2 region (Los Angeles).

July 02, 2018

Fixed a bug in auto scaling configuration where App Engine was aggressively shutting down instances when the max_instances setting was used.

May 15, 2018

  • Completed a gradual rollout of an upgrade to the automatic scaling system:
    • Improved efficiency resulting generally in lower instance cost (up to 6% reduction for many users) and up to 30% reduction for loading requests, which are the first request to a new instance.
    • New max instances setting allows you to cap the total number of instances to be scheduled.
    • New min instances setting allows you to specify a minimum number of instance to keep running for your app.
    • New target CPU utilization setting lets you optimize between latency and cost.
    • New target throughput utilization setting lets you optimize for the number of concurrent requests at which new instances are started.
    • No more resident instances in auto scaling. Previously, if you used the min_idle_instances setting, the minimum idle instances were labelled as Resident in the Cloud Console, with the remainder of the instances labelled as Dynamic. The new scheduler simply labels all instances as Dynamic with auto scaling. However, the underlying behavior remains similar to previous behavior. If you use min_idle_instances and enable warmup requests, you will see at least that many dynamic instances running even during periods with no traffic.
    • For more details, see the auto scaling documentation.

December 14, 2017

October 31, 2017

  • App Engine is now available in the asia-south1 region (Mumbai, India).

October 11, 2017

September 13, 2017

  • You can now use managed certificates to add SSL to your custom domain. Once you map your custom domain to your application, App Engine provisions an SSL certificate automatically and handles renewing the certificate before it expires and revoking it if you remove the custom domain. Managed certificates are in beta. For more information, see Securing Custom Domains with SSL.

September 05, 2017

  • App Engine is now available in the southamerica-east1 region (São Paulo, Brazil).

August 01, 2017

  • App Engine is now available in the europe-west3 region (Frankfurt, Germany).

July 18, 2017

  • App Engine is now available in the australia-southeast1 region (Sydney, Australia).

June 06, 2017

  • App Engine is now available in the europe-west2 region (London).
  • App Engine is now available in the australia-southeast1 region (Sydney, Australia).

May 09, 2017

  • App Engine is now available in the us-east4 region (North Virginia).

October 27, 2016

  • The Channel and XMPP services are now deprecated. These services will be turned down on October 31, 2017.

August 01, 2016

Admin API notes

  • Version 1 of the Admin API is now generally available.

Version 1.9.42

Ruby 2.5 runtime notes

  • This release does not include a new Ruby 2.5 SDK. Ruby 2.5 users should continue to use the 1.9.40 SDK.

July 18, 2016

Version 1.9.40

  • Version 1.9.39 was skipped.
  • LeaseTasksByTag requests will be limited to 25 requests per second.
  • Server Errors and Client Errors now more accurately reflect per-URL status errors in the App Engine dashboard.
  • New App Engine guided walkthrough in the Cloud Console. Pick your preferred language and launch an interactive tutorial directly in the console.
  • Increases the maximum cron tasks limit to 250.

July 01, 2016

Cloud Datastore

May 25, 2016

Version 1.9.38

  • The error returned by URL Fetch for a request to a port outside of the permitted ranges (80-90, 440-450, 1024-65535) will now always return INVALID_URL as documented.

Cloud Datastore

  • When committing a cross-group transaction, version numbers returned for new or updated entities are all the same. With the previous behavior, entities within the same group committed as part of a cross-group transaction, had the same version number, but entities in different groups might have had different version numbers. This change ensures all new and updated entities have an identical version number, regardless of their entity group, when committed as part of a cross-group transaction. As before, entities that are not updated will not have a new version number.

May 04, 2016

Version 1.9.37

Includes general bug fixes and improvements.

May 02, 2016

App Engine flexible environment

  • The Ruby runtime is now available for the App Engine flexible environment.

April 18, 2016

Version 1.9.36

In response to your requests, the App Engine Users API joins the rest of App Engine in supporting IAM roles and group expansion. This means that any user who is a project Owner, Editor or Viewer or an App Engine Admin is considered an "admin" by the Users API, regardless of whether the user was granted the role directly or by membership in a group. * This release populates error details, when available, in error messages associated with the "OverQuota" exception type.

March 24, 2016

Version 1.9.35

  • Fixes trace timestamps to match log timestamps.

March 04, 2016

Version 1.9.34

  • Increases default quota for URL fetch for billed apps. Refer to the Quotas page for details.

February 17, 2016

Version 1.9.33

  • The URL path "/form" is now allowed and will be forwarded to applications. Previously, this path was blocked.

February 03, 2016

Version 1.9.32

  • Container construction choices for Managed VMs

    The gcloud preview app deploy (and mvn gcloud:deploy) commands upload your artifacts to our servers and build a container to deploy your app to the Managed VM environment.

    There are two mechanisms for building the container image remotely. The default behavior is to build the container on a transient Compute Engine Virtual Machine which has Docker installed. Alternatively, you can use the Cloud Build service. To use the Cloud Build service, follow these steps:

    1. Activate the Cloud Build API for your project.
    2. Use the command gcloud config set app/use_cloud_build True. This will cause all invocations of gcloud preview app deploy to use the service. (To return to the default behavior, use the command gcloud config set app/use_cloud_build False.

January 14, 2016

Version 1.9.31

App Engine now supports Google Groups: Adding a Google Group as a member of a project grants the members of the group access to App Engine. For example, if a Google Group is an Editor on a project, all members of the group now have Editor access to the App Engine application.

November 30, 2015

Version 1.9.30

Headers for push queue requests made for Task Queue tasks with no payload will now contain a Content-Length entry set to '0'. Previously headers for such requests contained no Content-Length entry.

Version 1.9.29

  • Stop calculating and storing queue depth for non-existent queues, queues marked for deletion, and in the case of queue table outages.
  • For developers using the endpoints API, added a discoverable boolean parameter to the @Api annotation to allow users to disable API discovery. Using this feature will prevent some client libraries (e.g. JavaScript) and the API Explorer from working, as they depend on discovery.

October 29, 2015

Version 1.9.28

The Prospective Search API, which was deprecated on July 14, 2015, is now restricted to existing users. It will fully shutdown on December 1, 2015. * Improved accuracy of Geo filtering in Search queries.

September 25, 2015

Version 1.9.27

Applications that are newly enabled for billing now default to an unlimited daily budget, and no longer default to a maximum daily budget of $0. This prevents unwanted outages due to running out of budget. To set a ceiling on your application's daily cost, after you enable billing, set a budget in the app engine settings. For more information, see Setting a daily budget.

Datastore

  • Bugfix: Repeated numeric facets are now allowed.
  • Faceted Search is now GA.

August 27, 2015

Version 1.9.26

  • oauth2client library upgraded to version 1.4.2
  • Adds "show in context" menu for MVM application logs that have thread_id or request_id as a field in their log entry. This allows sorting app logs based on either field.
  • Capability to provision applications for current load and configure elastic provisioning based on both VM and application level metrics.
  • Remote API can now be accessed using OAuth2 credentials using https://developers.google.com/identity/protocols/application-default-credentials
  • Use RequestPayloadTooLargeException for URLFetch requests with payloads that are too large.

August 14, 2015

Version 1.9.25

  • Added PyAMF version 0.7.2 (Beta).
  • Admin Console menus start redirecting to Cloud Console. Select services such as the Admin Logs will continue to be available in the Admin Console.
  • Datastore now allows properties to represent the empty list.
  • Failed tasks in queues configured with a retry_limit of zero will no longer be retried.