Cloud Storage objects now expose `zonalAvailabilityInfo` in their metadata, detailing their presence in Rapid Cache Ultra (RCU) zonal caches. This includes a list of `availableZones` where the object has a zonal copy.
This Vertex AI v1beta1 update introduces new breaking changes by making `task` and `parent` parameters strictly required for specific agent task methods. However, it also rolls back previous breaking changes by making `Agent.status` and `AgentStatus.state` writable again. Key new features include Omni LoRA tuning for advanced model customization, expanded OAuth scopes for Discovery Engine integration, and new agent task management capabilities.
Vertex AI has reversed a recent update, making `Agent.status` and `AgentStatus.state` properties writable once more, restoring developer control. Additionally, many `operations.get` methods now support new Discovery Engine-related OAuth scopes, indicating deeper integration with Agentspace, Vertex AI Search, and NotebookLM Enterprise.
The recently added Zstd compression algorithm option for Pub/Sub messages has been removed. Developers using or planning to use Zstd compression should revert to other supported algorithms.
The `ComponentMetrics` schema in the Looker API has a breaking change: the `componentType` property has been renamed to `type`. Developers must update their integrations to use the new property name.
This update introduces breaking changes by making `packageName` and `token` strictly required in certain contexts and `transitionState` read-only. Developers can now programmatically manage subscription plan transitions with new `cancelplantransition` and `scheduleplantransition` methods.
Cloud Pub/Sub now supports Zstd as a compression algorithm for messages. Developers can leverage Zstd for potentially better compression ratios and performance, offering more options for optimizing message throughput and storage.
Dataform introduces `createLongRunning` for asynchronous Workspace creation. This new method requires the `parent` parameter, which is a breaking change if you were previously omitting it in early integrations.
The `anywhereCaches.pause` method has been removed from the Cloud Storage API, which is a breaking change for integrations managing Anywhere Cache instances. Additionally, the `BucketStorageLayout` schema now includes `rapidCacheInfo` to expose details about Rapid Cache configurations.
The Gmail API has rolled out a comprehensive set of new, granular OAuth2 scopes, enabling developers to request more precise permissions for drafts, messages, labels, and filters. This update aims to enhance security and user privacy by promoting the principle of least privilege.
The `serviceAccountId` fields in `AwsAccessRole` and `AzureProperties` are now read-only, a breaking change. New `serviceDirectoryService` fields enable private network connections to AWS and Azure via Cross-Cloud Interconnect.
BigQuery now provides detailed information about installed packages within routine build statuses and introduces a new schema for IAM policy members on tables. Be aware of breaking changes as several properties across `InstalledPackage`, `ResourcePolicyMember`, `RoutineBuildStatus`, and `Table` schemas have been made read-only.
The `Approval` schema in the Google Drive API now includes an `approvedRevisionId` property, providing the file's revision ID upon successful approval.
Discovery Engine introduces new APIs for managing UserAvailability resources, including batch updates and listing. However, this update includes breaking changes: `name` and `parent` parameters are now strictly required in certain contexts, and `verification` and `updateTime` properties are now read-only.
Dataplex introduces a new `BatchOperationMetadata` schema for detailed insights into long-running batch operations. Be aware of breaking changes as several properties within this new schema are explicitly read-only. Additionally, access scopes for `entryLinks.get` have been updated.
A breaking change makes the `verification` field in `EngineFeaturePolicyMember` read-only. Additionally, Discovery Engine now supports granular per-feature access policies on `Engine` resources, allowing you to control which users or groups can utilize specific engine features.
This update introduces granular feature access policies for Discovery Engine instances, allowing you to control who can use specific features. A breaking change makes the `verification` field in `EngineFeaturePolicyMember` read-only.
The Data Catalog v1beta1 API has undergone a significant and breaking change, with nearly all methods and schemas related to entries, entry groups, and tag templates being removed. This constitutes a major rollback and effective deprecation of the v1beta1 API surface.
The Data Catalog V1 API has undergone a substantial breaking change, with numerous methods and schema properties removed. Developers relying on entry groups, entries, tags, and tag templates will need to update their integrations.
Cloud Composer environments can now be provisioned in an X-Extra Large size. Additionally, `DEVELOPMENT` mode environments can configure scheduled hibernation and resumption, enabling cost savings and automated management.
Cloud Composer now allows you to hibernate and resume environments, enabling significant cost savings for development and intermittent workloads. Additionally, a new X-Extra Large environment size is available for more demanding use cases.
Application Integration now supports a `WORKFLOW_TEXTPROTO` file format for specific upload/download operations, enabling a new way to manage integration definitions. Additionally, a `validateOnly` option has been added to the publish request, allowing pre-flight checks without actual deployment.
BigQuery introduces cross-region dataset replication and disaster recovery capabilities, along with significant enhancements for Python UDFs. Be aware of breaking changes where several job and replica statistics properties are now read-only.
This Vertex AI v1beta1 update introduces significant breaking changes, making several parameters required and many properties read-only. Developers must adapt to the removal of the `media.upload` method and the retraction of recently added `idpNonce` and `ids` parameters. On the feature side, the API sees a massive expansion in GenAI capabilities, including detailed interaction tracking, new content types, and comprehensive agent task management, alongside the re-introduction of `continuationToken` for long-running GenAI operations.
This update introduces breaking changes by making several agent-related schema properties read-only and removing recently added parameters. On the feature side, Vertex AI Agents gain significant new configuration options for identity, memory, encryption, and persona. A new method allows setting default Notebook Runtime Templates, and GenAI models get new capabilities like Bash code execution and video upscaling.
The `ThumbnailDetails` schema now includes a new `shortsAspectRatio` property, providing access to 9:16 aspect ratio thumbnails specifically for YouTube Shorts. This allows developers to better display Shorts content.
The BigQuery Reservation API now includes a new `upgradeEdition` method, allowing programmatic upgrades of reservation editions (e.g., Standard to Enterprise). This enables more flexible management of your BigQuery capacity.
This update introduces breaking changes by making several fields read-only across Engine, Project, and AssistAnswer schemas. Developers must update any code attempting to write to these properties. Additionally, new capabilities include customer-managed OAuth scopes for connectors, global feature toggle controls for engines, and the ability to specify provisioning intent for projects.
Discovery Engine introduces new controls for global feature rollout stages and provides read-only access to effective feature states. However, this update includes significant breaking changes as many properties related to engine configuration, project experience, and tool display names have been made read-only.
This update introduces several breaking changes where numerous API properties have been made read-only. Developers must update their code if they were previously writing to these fields. Additionally, new capabilities for managing feature toggles, provisioning project experiences, and custom OAuth scopes are now available.
Dataform now offers an asynchronous method for creating workspaces, `createLongRunning`, which requires a `parent` parameter. You can also set a `concurrentActionsLimit` in `InvocationConfig` for finer control over workflow execution.
Dataform now allows developers to set a maximum concurrent actions limit for workflow invocations. A new `QUEUED` state for actions provides visibility into concurrency-related delays.
AlloyDB's autoscaling policies for read pools can now leverage connection count as a scaling metric. This allows for more granular control, enabling dynamic adjustments based on the number of active database connections.
AlloyDB v1beta now introduces a new autoscaling policy type based on connection count. You can configure your autoscaler to scale instances based on a target number of connections.
AlloyDB introduces a new `connectionsCount` policy for autoscaling, allowing you to scale instances based on the target number of active connections. This provides finer-grained control over resource allocation.
Email Alert Preferences
Stay notified of breaking changes and schema evolutions
Instant Breaking Alerts
Email notification within 1 hour of any removed method or breaking schema evolution.
Weekly Monday Digest
Curated summary of new APIs, beta promotions, and high-impact updates.
Zero Spam Guarantee
1-click unsubscribe anytime. Only verified Google accounts.
