GCP Release Note: July 15, 2025

App Engine flexible environment Go

Feature

Support for Go 1.24 runtime is in Preview.

App Engine standard environment Go

Feature

Support for Go 1.24 runtime is in Preview.

BigQuery

Feature

You can now commercialize your BigQuery sharing listings on Google Cloud Marketplace. This feature is generally available (GA).

Feature

You can flatten JSON columns in BigQuery data preparation with a single operation. This feature is generally available (GA).

Cloud Run

Feature

Compute flexible committed use discounts (CUDs) have expanded to also cover your Cloud Billing account’s spend across Cloud Run services with request-based billing and Cloud Run functions.

The improved spend-based CUD experience is available without requiring an opt-in for new users or users who don’t have an active spend-based CUD.

To learn more about how opting into the new model affects your flexible CUDs, see Committed use discounts.

Feature

Support for the Go 1.24 runtime is in Preview.

Cloud Run functions

Feature

Support for the Go 1.24 runtime is in Preview.

Compute Engine

Changed

Compute flexible committed use discounts (CUDs) offer expanded coverage by
supporting the following resources and services:

• Memory-optimized M1, M2, M3, and M4 VMs
• Compute-optimized H3 instances
• Cloud Run services with request-based billing
• Cloud Run Functions

To receive the expanded coverage for flexible CUDs, you must opt in to the new
spend-based CUD model. Cloud Billing accounts that meet specific criteria are
automatically opted into the new model. On January 21, 2026, all remaining
accounts will automatically migrate to the new model. You can opt in before that
date to start receiving the expanded coverage. To learn more about the new model
and the opt-in details, see
Spend-based CUDs program improvements.

To learn more about this change and how your flexible CUDs apply after you opt
in, see
Compute flexible CUDs.

Dataproc

Announcement

Dataproc on Compute Engine: Starting August 18, 2025, the following diagnostic properties will be enabled by default for newly created Dataproc clusters:

• dataproc:diagnostic.capture.enabled: Enables the collection of checkpoint data in the cluster temp bucket.
• dataproc:dataproc.logging.extended.enabled: Enables the collection of logs for the Knox, Zeppelin, Ranger-usersync, Jupyter_notebook, Jupyter_kernel_gateway components and the Spark History-Server in Cloud Logging.

• dataproc:dataproc.logging.syslog.enabled: Enables the collection of VM syslogs in Cloud Logging.

  To continue using the Ops Agent initialization action opsagent.sh to ingest syslogs from Dataproc cluster nodes, do one of the following:

  • Recommended: Use opsagent_nosyslog.sh since
    VM syslogs will now be emitted by default from Dataproc clusters.
  • Set the dataproc:dataproc.logging.syslog.enabled=false and continue using opsagent.sh
    to ingest syslogs.

Note: To disable any of these features, set the corresponding property to false during cluster creation.

Announcement

New Dataproc on Compute Engine subminor image versions:

2.3.6-debian12, 2.3.6-ubuntu22, and 2.3.6-rocky9.

Feature

Dataproc now allows Dynamic update of multi-tenancy clusters.

Pub/Sub

Libraries

General availability: The Go Pub/Sub client library has a new major version. For more information on how to migrate from v1 to v2, see the Migration guide.

Deprecated

Source: Google Cloud Platform