The `backupId` field in `WorkloadCapture` is now read-only, requiring updates for any code attempting to set it. Additionally, `DatabaseInstance` gains new controls for Database Center integration and major version upgrade prechecks.
Vertex AI's v1beta1 API now offers powerful new capabilities for video generation, including LoRA for stylization and Pro Super Res upsampling. Agents gain more control with default model configurations, and evaluation runs can now utilize cross-region models.
Vertex AI introduces LoRA and Super Resolution configurations for large vision model video generation experiments. Agents can now specify a default model and temperature, and evaluation runs gain cross-region model flexibility.
The `PostToQueueWithTriggerIdRequest` schema now includes a `workflowId` field, allowing you to target specific, even unpublished, versions of your integrations for testing.
A breaking change has made the `eucHardeningDisposition` field read-only in `IntegrationVersion`. Additionally, new parameters and response fields are available for `TestIntegrationsRequest` and `TestIntegrationsResponse`, offering more control and insight into credential flows and EUC hardening during integration testing.
Discovery Engine now allows linking conversation feedback to specific Sobi agent tasks via a new `taskName` field. Minor internal scope adjustments were also made for `completeQuery` methods.
Discovery Engine v1alpha introduces breaking changes: the `autoModelId` field in widget configurations is now read-only, and the `name` parameter for the new `toolCalls.operations.get` method is strictly required. Additionally, a new `get` method for tool call operations and a `taskName` field for conversation feedback are now available.
A breaking change makes the `autoModelId` property in `WidgetConfigUiSettingsModelConfigInfo` read-only. Additionally, `FeedbackConversationInfo` now includes `taskName` for tracking Sobi long-running agent tasks, and `completeQuery` methods see scope reordering.
Dataplex has removed all API surface related to unstructured data profiling and graph profiling. This includes schema properties for data discovery, data scans, and detailed graph profile configurations. Developers using these experimental features must update their integrations.
BigLake now offers full IAM policy management for Views with new `getIamPolicy`, `setIamPolicy`, and `testIamPermissions` methods. Heads up: The `resource` parameter is now strictly required across the API, which is a breaking change.
Looker instances now expose their configured authentication types, including Google Auth and Workforce Identity Federation, through a new `authType` field. This provides clearer insight into instance security configurations.
Cloud Storage buckets now support a 'hard delete pause' configuration within their soft delete policy. This new feature allows administrators to temporarily prevent the permanent deletion of soft-deleted objects, offering an additional layer of data protection.
Vertex AI v1beta1 introduces custom voice management, allowing creation and listing of personalized voices. It also adds granular cache configuration updates. Be aware of several breaking changes, including new read-only fields and a type change for `structuredPrompt` in video generation. A previous breaking change regarding `A2ATaskRecord` read-only fields has been rolled back.
Vertex AI introduces a new `ServingProfile` resource for managing model serving configurations. This update also includes several breaking changes, notably making `parent` and `name` parameters strictly required, and changing the type of `structuredPrompt` in vision models. OAuth scopes for `agents` methods have also been adjusted.
Dataplex now exposes standard IAM policy management methods for `agentTasks` resources. Developers can programmatically get, set, and test IAM policies directly on their agent tasks, enhancing security and access control.
AlloyDB v1beta now supports Express clusters via a new `expressConfig` property on the `Cluster` schema. Developers should note significant breaking changes: several observability and query insights properties on `Instance` and related schemas are now read-only.
AlloyDB v1alpha now supports creating Express clusters. Be aware of breaking changes: several observability and query insights fields on `Instance` are now read-only, becoming output-only information.
AlloyDB instances now expose `observabilityInstanceInfo` and `queryInsightsInfo` as output-only fields. Any existing code attempting to modify these properties will now encounter errors, as they are strictly immutable. Update your integrations to treat these as informational.
The `imageUrl` property in `CommentSnippet` is now read-only, meaning developers can no longer set it. Additionally, several media upload endpoints now accept a broader range of content types.
Datastream now provides new configuration options for SQL Server change tables, enabling automated management of capture instances when DDL changes occur. This simplifies handling schema evolution.
The Google Workspace Admin Reports API now supports auditing for Gemini Notebook activities. Developers can use the `activities.list` method to retrieve these new reports.
