Cloud Billing Budgets now supports a new `spendCap` feature, allowing you to define and enforce spending limits directly within your budgets. This introduces a new `SpendCap` schema with `inputState` for control and `outputState` for monitoring.
Cloud Storage introduces a new `objects.viewFullContext` method to retrieve detailed object context, defined by the new `ObjectFullContext` schema. While the diff reports breaking changes, these apply to the required parameters of this *new* method, not existing API calls.
BigQuery introduces a new `secureContext` for passing sensitive, context-specific information to queries, accessible via a new SQL function. Additionally, you can now export Parquet data with native Geography types. Heads up: `JobStatistics2.referencedLogicalViews` is now read-only, which may break existing integrations.
The `connectorDisplayNames` property in both `GoogleCloudDiscoveryengineV1alphaAssistAnswer` and `GoogleCloudDiscoveryengineV1betaAssistAnswer` schemas has been made read-only. This is a breaking change for applications that may have been writing to this field.
A breaking change makes `connectorDisplayNames` in `AssistAnswer` read-only, requiring updates if you were writing to it. Additionally, a new `basicAuthenticationEnabled` field provides more flexibility for OAuth integrations.
The `connectorDisplayNames` property in the `AssistAnswer` schema (v1 and v1alpha) is now `readOnly`. This is a breaking change for developers who were previously writing to this field, which provides human-readable names for internal connector agents.
The `trackActiveQueryPlan` property within AlloyDB's `ObservabilityInstanceConfig` schema has been deprecated. Developers should plan to migrate away from using this feature.
The `trackActiveQueryPlan` field within the `ObservabilityInstanceConfig` schema has been marked as deprecated. Developers should update their configurations to avoid using this field.
AlloyDB now supports new `userType` enum values for IAM group-based authentication, enabling more flexible and granular control over database access for groups, users, and service accounts.
The YouTube Data API v3 has undergone significant breaking changes. The `postId` parameter and properties have been removed from comments and comment threads. Additionally, `favorite` and `like` activity types and their associated schemas are no longer available. On a positive note, the `subscription` activity type is no longer deprecated.
The Google Drive API's documentation for `permissions.create`, `delete`, and `update` methods has been updated. The warning about concurrent permission modifications is now more explicit, clarifying its scope.
The Google Drive API's permission methods (`delete`, `insert`, `patch`, `update`) now feature updated descriptions that clarify the scope of concurrent modification warnings.
The Dataplex API has undergone significant breaking changes, with the complete removal of the Data Taxonomy and Data Attribute Binding feature sets. Developers using these features must update their integrations immediately. A new IAM role configuration for Data Product Access Groups has been introduced.
The Android Publisher API now supports larger deobfuscation file uploads, with the maximum size increased from 1.6 GB to 2.0 GB. This update benefits developers with larger apps.
Cloud Pub/Sub introduces new schemas, `PublishOperation` and `PubsubClientTelemetry`, to provide more detailed client-side telemetry for publish operations, including hedging attempts and client-side start times.
The Pub/Sub API now includes new schemas for client-side telemetry, `PubsubClientTelemetry` and `PublishOperation`. These additions provide insights into publish operations, such as hedging attempts and client-side publish start times, to aid in debugging and performance analysis.
New `PubsubClientTelemetry` and `PublishOperation` schemas provide client-side debugging information for publish calls, including hedging attempts and start times.
Dataproc Metastore now exposes `LakehouseProxyConfig` for managing phased migrations to Lakehouse Iceberg REST Catalogs. This new configuration and its properties are read-only, which is a breaking change for any clients attempting to write to them.
The Metastore v1alpha API introduces Lakehouse proxy configuration for phased namespace migrations. The new 'lakehouseProxyConfig' field in the Service schema and its sub-properties are now explicitly read-only, which is a breaking change.
Dataproc Metastore introduces new Lakehouse proxy routing capabilities for phased migrations to Iceberg REST Catalogs. The new `LakehouseProxyConfig` and its properties are now officially read-only, which is a breaking change if you were previously attempting to configure them.
Adds BillingAccountLicenseConfig schema properties and refines parameter documentation for suggestions, searches, and user events.
Introduces operations get method for collaborative project knowledge spaces, updates agent sharing configuration scopes, and adds widget and billing license properties.
Updates Discovery Engine v1 schemas, introducing read-only tag properties to WidgetConfigCollectionComponent and adding BillingAccountLicenseConfig.
A minor documentation update clarifies the reference point for file paths within Dataform workspaces. No functional changes or developer action required.
The `UpdateAppStoreHostedAppResponse` now includes an `updateId` to uniquely identify and track specific versions of hosted app updates, enabling correlation with publishing signals.
Analytics Hub now provides advanced customization for Pub/Sub to Bigtable ingestion. Developers can define custom row keys using delimited fields or structured schemas, and control how JSON message fields map to Bigtable column families, offering greater flexibility for data modeling.
Looker's export process now provides granular telemetry via new ExportMetrics and ComponentMetrics schemas, alongside support for self-hosted instance sources.
Dataplex now provides granular observability for LLM-powered data documentation scans, including detailed token usage and compute unit consumption.
Vertex AI v1beta1 shifts Agent updates to Long Running Operations and introduces experimental 'Pro Edit' video capabilities. New observability features and Reasoning Engine garbage collection also debut.
Vertex AI introduces experimental video editing capabilities and OpenTelemetry-based observability for Agents. Notably, updating an Agent via patch is now a long-running operation.
AlloyDB v1beta introduces support for PostgreSQL 19 and a new Edition classification for clusters, including a Developer edition. Note that the edition field on Backups is now read-only.
AlloyDB v1alpha introduces support for Postgres 19 and a new edition classification for clusters, while making the edition field read-only on backups.
The Directory API documentation now explicitly details the HTTP response codes returned when resolving unmanaged user account conflicts during user creation.
Discovery Engine adds resource-level IAM filtering for Gemini Enterprise and dynamic search-as-you-type scoring overrides. Alpha users also gain support for file attachments in long-running agent tasks.
This update introduces resource-level access controls for Gemini Enterprise, per-request Search-As-You-Type overrides, and a breaking change to widget model configurations.
Discovery Engine adds granular scoring controls for Search-as-you-type and resource-level IAM filtering for Gemini Enterprise. A breaking change makes the widget 'family' field read-only.
Developers can now explicitly flag if APK sets are already published on Google Play and provide a corresponding version code.
Analytics Hub now supports Customer-Managed Encryption Keys (CMEK) for Query Templates, allowing developers to encrypt template definitions using their own KMS keys.
Cloud SQL adds a new suite of methods to capture production database traffic and replay it on test instances for performance and upgrade validation.
The Cloud SQL Admin API introduces strict validation and immutability rules for Workload Capture schemas, alongside new methods to list, start, stop, and replay database workloads.
A breaking change in the Metastore v1beta API marks the MigrationSummary endTime field as read-only. The createTime field description has also been updated to clarify its role in the migration process.
The MigrationSummary schema now marks endTime as read-only and redefines createTime to reflect the start of metadata reads.
The MigrationSummary schema has been updated with a new read-only endTime field and revised semantics for createTime.
Dataproc's AttachedDiskConfig schema has deprecated the diskType field, introducing a new type field for specifying Hyperdisk configurations.
Cloud Storage has added an extendedDataTypeUrl field to the ObjectCustomContextPayload schema to better identify custom context data.
The NotebookLM alpha API surface has been reinstated after a recent removal, now featuring stricter parameter requirements and immutable fields.
BigQuery now supports mounting GCS buckets as volumes for Python UDFs and introduces a native UUID data type for SQL schemas.
A minor documentation update for Vertex AI Agents changes references from 'GCP' to 'Google Cloud' in the AgentTool schema.
Dataform now supports native BigQuery unit testing and granular end-user authentication for workflow invocations. Note that several metadata fields for unit tests and auth are now strictly read-only.
Dataform introduces native support for BigQuery unit tests and granular execution modes. Several fields related to test results and authentication are now strictly read-only.
Vertex AI Agent Builder adds native Sensitive Data Protection integration for data stores and connectors, alongside new session management controls and model 'thinking' levels.
This update includes a massive breaking change removing the NotebookLM alpha API surface while introducing new Sensitive Data Protection integrations and session management controls.
Discovery Engine introduces Sensitive Data Protection (DLP) integration, configurable session management for Engines, and a breaking change making icon URLs read-only.
A specific developer account permission related to public/private app visibility has been deprecated and is no longer supported.
The API documentation now explicitly states that all APKs within an AppStoreAppActiveApkSet must belong to the same app version.
Developers can now secure sensitive transfer credentials using Secret Manager instead of raw strings. This update also marks specific configuration fields as read-only, which may impact generated client libraries.
Vertex AI v1beta1 enforces mandatory name and parent parameters and transitions many resource fields to read-only status. Additionally, the API is shifting its primary OAuth scope to the service-specific aiplatform scope.
Vertex AI is promoting the specific `aiplatform` OAuth scope as the primary authorization method across most resources, while finalizing the enforcement of the `name` parameter as strictly required.
The Directory API now supports expiring role assignments, allowing administrators to set a specific timestamp for when a user's role should be automatically revoked.
The Drive API now allows developers to include comments when duplicating files via the files.copy method.
The description for the principal field in the Assignment resource has been updated for clarity and grammatical consistency.
The videos.getRating method now supports the youtube.readonly scope, allowing for more restricted access to rating data.
The Cloud Billing API has introduced a new interaction model involving 'agents' and 'tasks', while enforcing stricter requirements on existing parameters.
The API now supports reporting for external content link transactions and introduces redemption limits for game-specific one-time product offers.
