App Engine standard environment for Go 1.12+ release notes

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

Go 1.23 is now available in preview.

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.

Go 1.22 is now generally available.

Starting in Go version 1.22 and later:

• You can't use go get outside of a module in the legacy GOPATH mode (GO111MODULE=off).
• Go recommends that you use a go.mod file for managing dependencies.

For more information, see Specify dependencies.

Go 1.22 is now available in preview.

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.

Go 1.21 is now generally available.

Go 1.21 is now available in preview.

The Search API is now available in the App Engine legacy bundled services for second-generation runtimes. Access this legacy bundled service through the App Engine services SDK for Go 1.12+.

The Go 1.20 runtime for App Engine standard environment is now generally available.

The Go 1.20 runtime for App Engine standard environment is now available in preview.

The Go 1.18 and Go 1.19 runtimes for App Engine standard environment are 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 Go 1.18 and Go 1.19 runtimes for App Engine standard environment are 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.

The App Engine legacy bundled services for Go 1.12+ are now available at the General Availability release level. These APIs can be accessed through language-idiomatic libraries. Calls to these API are billed according to the standard rates.

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.

The Go 1.16 runtime for App Engine standard environment is now generally available.

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.

Many legacy App Engine APIs are now available to select second-generation runtimes. These APIs are available for Go 1.12+ in preview, through language-idiomatic libraries. Calls to these APIs are billed according to the standard rates.

The Go 1.16 runtime for App Engine standard environment is now available in Public Preview.

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.

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.

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

Build environment variables support is now available in preview.

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

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

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.

The Go 1.15 runtime for the App Engine standard environment is now generally available.

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.

The Go 1.14 runtime for the App Engine standard environment is now generally available.

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

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.

The Go 1.14 runtime Beta for the App Engine standard environment is now available.

The Go 1.13 runtime for the App Engine standard environment is now generally available.

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

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.

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

App Engine is now available in the asia-northeast3 region (Seoul).

App Engine is now available in the us-west3 region (Salt Lake City, Utah).

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.

• Serverless VPC Access is now GA.

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

• Updated Go SDK version to 1.9.71:

  • Support for Go versions 1.9 and older has been removed.
  • The goapp tool has been removed.
  • The Go 1.9 GOROOT directory has been removed.

• The Go 1.12 runtime on the App Engine standard environment is now generally available.

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

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

• The Go 1.12 runtime for the App Engine standard environment is now in beta.

• A migration guide for moving apps from Go 1.9 to Go 1.12 is available.

• The Go 1.11 runtime for the App Engine standard environment is now GA.

• Updated Go SDK to version 1.9.70.

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

• The Go 1.11 runtime for the App Engine standard environment is now in beta.

• A migration guide for moving apps from Go 1.9 to Go 1.11 is available.

• Updated Go SDK to version 1.9.68.

• Updated Go SDK to version 1.9.67.

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

• Updated Go SDK to version 1.9.66.

• The local development server now prints the process ID of the running process on startup. You can use the process ID when debugging your app.

• Updated Go SDK to version 1.9.65.

• Version 1.9 of the Go runtime is now generally available and is set as the default runtime for Go in the App Engine standard environment.

  Re-deploying all new and existing applications using api_version: go1, will now run on Go 1.9. To continue using other API versions, such as Go 1.6, you must specify api_version: go1.6 in your app.yaml file.

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

• Updated Go SDK to version 1.9.64.

• App Engine flexible environment applications that declare runtime: go in their app.yaml configuration file now deploy with the Go 1.10 runtime.

• Updated Go SDK to version 1.9.63.

• Added beta support for version 1.9 of the Go runtime.

  You can try out Go 1.9 by specifying api_version: go1.9 in your app.yaml configuration file.

  To use the 1.9 beta version, you must first update your Go SDK to 1.9.63 or later. For details about downloading and installing the SDK, see the Downloads page.

  During the beta period, api_version: go1 continues to be an alias for go1.8. Note that go1.9 is not guaranteed to work correctly while it is in beta. We are relying on user feedback to ensure that go1.9 meets users' needs before promoting it to a GA release. Post feedback to the google-appengine-go Google Group.

• Updated Go SDK to 1.9.62

• Includes internal updates for how applications are deployed.

• Improved access control documentation around deploying apps with IAM roles and service accounts:

  • Predefined App Engine roles
  • Deploying using IAM roles
  • Require permissions

• Updated Go SDK to 1.9.61

• Add --go_debugging flag to dev_appserver.py to enable Delve debugging.

• Add -debug flag to goapp serve to enable Delve debugging.

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

• Updated Go SDK to version 1.9.60.

• Version 1.8 of the Go runtime is now generally available and is set as the default runtime for Go in the App Engine standard environment.

  Now, when you deploy any new or existing apps that use api_version: go1, those apps run on Go 1.8. To continue using Go 1.6, you must specify api_version: go1.6 in your app.yaml file.

  Before you can use the Go 1.8 runtime locally with dev_appserver.py or goapp, you must first update to the latest version of the SDK for App Engine.

  Changes that might affect your app:

  • As of Go 1.7, the context package has moved into the stdlib. You must ensure that your code and dependencies work correctly with this change. You can use the fix command to change your app's imports from "golang.org/x/net/context" to "context", for example: go tool fix -r context.
  • In Go 1.8, the internal representation of time.Time objects has changed and might break your app if you use either reflect.DeepEqual or == to compare time.Time values. Use time.Equal to compare timestamps.

• Announced general availability of App Engine firewall.

• Updated Go SDK to 1.9.59

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

• The gcloud commands and Admin API methods used to map custom domains are now generally available. This includes gcloud domains verify and apps.authorizedDomains.list. However, if you want to use managed SSL certificates, use the beta commands and methods that are specified in Securing Custom Domains with SSL.

• Updated Go SDK to version 1.9.58

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

• Beta release of the App Engine firewall.

• Updated Go SDK to version 1.9.57.

• Go 1.8 uses the new standard library context package when calling appengine.NewContext().

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

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

• Updated Go SDK to version 1.9.56

• Updated Go SDK to version 1.9.55

• Enable the Go 1.8 beta

This release adds beta support for go1.8. To use Go 1.8, set api_version: go1.8 in your app.yaml configuration file. You must also use App Engine SDK, not Cloud SDK. To download the App Engine SDK, go to the Downloads page and at the bottom of the page, expand the Or, you can download the original App Engine SDK for Go section.

Go 1.8 will be available with the next Cloud SDK release.

During the beta period, api_version: go1 will continue to be an alias for go1.6. Note that go1.8 is not guaranteed to work correctly while it is in beta. We are relying on user feedback to ensure that go1.8 meets our users' needs before promoting it to a GA release. Send feedback to the google-appengine-go google group.

• As of go1.7 the context package has moved into the stdlib. Ensure that your code and dependencies work correctly with this change.
• Note that go1.8 changes the way that local timezones and UTC are represented. If you use reflect.DeepEqual or == to compare time.Time values, this might be a breaking change. Instead, use time.Equal when comparing timestamps.

• App Engine is now available in the europe-west2 region (London).

• You can now use the beta-level features in the Admin API and gcloud command-line tool to create and manage your custom domains and SSL certificates.

• Updated Go SDK to version 1.9.54.

• api_version: go1 and api_version: go1.6 both use the new goroot-1.6 directory.

• Upgraded to Go 1.6.4

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

• Updated Go SDK to version 1.9.53.

• In preparation for the Go 1.8 beta, Go api_versions are mapped to specific GOROOT directories.

• Updated Go SDK to version 1.9.48.

• Updated Go SDK to version 1.9.46.

Admin API notes

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

Version 1.9.42

Go 1.12+ runtime notes

• This release does not include a new Go 1.12+ SDK. Go 1.12+ users should continue to use the 1.9.40 SDK.

Version 1.9.40

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

Cloud Datastore

• New Cloud Datastore Pricing is now in effect.

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.

Cloud Datastore

• App Engine Go runtime updated to Go 1.6.2.

Version 1.9.37 SDK uses the release tags go1.1–go1.6 when compiling with the development SDK to bring it inline with those used in typical Go 1.6 builds. Starting with the 1.9.37 SDK, all the necessary Go files in your gopath will be uploaded to the server regardless of the release tags they require. This will ensure that the server always has all the files it needs to compile your app regardless of the release tags being used. This addresses problems that may arise from mismatched release tags in the 1.9.35 SDK.

Version 1.9.37

App Engine flexible environment

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

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.

Version 1.9.35

• The SDK now includes support for vendoring external dependencies. See the go command documentation for more details.

Version 1.9.34

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

Version 1.9.33

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

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.

• Enabled response compression in Go runtime. This might reduce bandwidth usage for some users.

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.

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.

Version 1.9.28

Improved accuracy of Geo filtering in Search queries.

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.

Datastore

• Faceted Search is now GA.

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.

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.

• appengine/search:
  • Support offsets and cursors in search requests and responses.

• appengine/user:new
  • Add User.ClientID field.