<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Google Cloud Radar — Real-Time Google API &amp; Cloud Feed</title>
  <subtitle>Automated pre-release intelligence for Google APIs and Cloud services. Live API changes and breaking changes tracked from the Google Discovery Service.</subtitle>
  <link href="https://google-cloud-radar.com/atom.xml" rel="self" type="application/atom+xml" />
  <link href="https://google-cloud-radar.com" rel="alternate" type="text/html" />
  <id>https://google-cloud-radar.com/atom.xml</id>
  <updated>2026-11-13T00:00:00Z</updated>
  <author>
    <name>Google Cloud Radar</name>
    <uri>https://github.com/max-ostapenko/google-cloud-radar</uri>
  </author>
  
  <entry>
    <title>Object Zonal Availability Info Added</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-13-storage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-13-storage-v1</id>
    <published>2026-11-13T00:00:00Z</published>
    <updated>2026-11-13T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Storage" />
    <category term="Cloud Storage" />
    <category term="storage.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: New Tuning, Agent Features, Breaking Changes &amp; Rollbacks</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-13-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-13-aiplatform-v1beta1</id>
    <published>2026-11-13T00:00:00Z</published>
    <updated>2026-11-13T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI Agent Status Writable Again; Discovery Engine Scopes Added</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-13-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-13-aiplatform-v1</id>
    <published>2026-11-13T00:00:00Z</published>
    <updated>2026-11-13T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Zstd Compression Option Rolled Back</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-12-pubsub-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-12-pubsub-v1</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Pub/Sub" />
    <category term="pubsub.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Looker API: ComponentMetrics property renamed</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-12-looker-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-12-looker-v1</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Looker Core" />
    <category term="looker.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking Changes &amp; New Subscription Plan Transition APIs</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-12-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-12-androidpublisher-v3</id>
    <published>2026-11-12T00:00:00Z</published>
    <updated>2026-11-12T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>Pub/Sub Adds Zstd Compression Support</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-11-pubsub-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-11-pubsub-v1</id>
    <published>2026-11-11T00:00:00Z</published>
    <updated>2026-11-11T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Pub/Sub" />
    <category term="pubsub.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataform Workspaces Get Async Creation, `parent` Now Required</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-11-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-11-dataform-v1</id>
    <published>2026-11-11T00:00:00Z</published>
    <updated>2026-11-11T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Anywhere Cache &apos;pause&apos; method removed; Rapid Cache info added</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-10-storage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-10-storage-v1</id>
    <published>2026-11-10T00:00:00Z</published>
    <updated>2026-11-10T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Storage" />
    <category term="Cloud Storage" />
    <category term="storage.v1" />
  </entry>
  <entry>
    <title>Gmail API Introduces Granular OAuth Scopes</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-10-gmail-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-10-gmail-v1</id>
    <published>2026-11-10T00:00:00Z</published>
    <updated>2026-11-10T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Gmail API" />
    <category term="gmail.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking: Service Account IDs Read-Only; Private Connectivity for AWS/Azure</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-10-bigqueryconnection-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-10-bigqueryconnection-v1</id>
    <published>2026-11-10T00:00:00Z</published>
    <updated>2026-11-10T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Connection API" />
    <category term="bigqueryconnection.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Routine Package Details &amp; IAM Policy Members Added, Several Fields Now Read-Only</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-10-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-10-bigquery-v2</id>
    <published>2026-11-10T00:00:00Z</published>
    <updated>2026-11-10T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>New Revision ID for File Approvals</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-08-drive-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-08-drive-v3</id>
    <published>2026-11-08T00:00:00Z</published>
    <updated>2026-11-08T00:00:00Z</updated>
    <summary type="text">The `Approval` schema in the Google Drive API now includes an `approvedRevisionId` property, providing the file&apos;s revision ID upon successful approval.</summary>
    <category term="Data Analytics" />
    <category term="Google Drive API" />
    <category term="drive.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: User Availability APIs &amp; Breaking Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-08-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-08-discoveryengine-v1alpha</id>
    <published>2026-11-08T00:00:00Z</published>
    <updated>2026-11-08T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataplex Batch Operations Get Detailed Metadata, Scope Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-08-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-08-dataplex-v1</id>
    <published>2026-11-08T00:00:00Z</published>
    <updated>2026-11-08T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: Per-Feature Access Policies &amp; `verification` Field Now Read-Only</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-07-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-07-discoveryengine-v1beta</id>
    <published>2026-11-07T00:00:00Z</published>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: Feature Access Policies &amp; Breaking Change</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-07-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-07-discoveryengine-v1</id>
    <published>2026-11-07T00:00:00Z</published>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Data Catalog v1beta1 API: Massive Breaking Changes &amp; Rollback</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-07-datacatalog-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-07-datacatalog-v1beta1</id>
    <published>2026-11-07T00:00:00Z</published>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Data Catalog" />
    <category term="datacatalog.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Major Breaking Change: Data Catalog V1 API Surface Significantly Reduced</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-07-datacatalog-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-07-datacatalog-v1</id>
    <published>2026-11-07T00:00:00Z</published>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Data Catalog" />
    <category term="datacatalog.v1" />
  </entry>
  <entry>
    <title>Composer Adds X-Extra Large Size &amp; Scheduled Hibernation</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-07-composer-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-07-composer-v1beta1</id>
    <published>2026-11-07T00:00:00Z</published>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Composer" />
    <category term="composer.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Hibernate/Resume Composer Environments, New X-Extra Large Size</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-07-composer-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-07-composer-v1</id>
    <published>2026-11-07T00:00:00Z</published>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Composer" />
    <category term="composer.v1" />
  </entry>
  <entry>
    <title>New Workflow Text Proto &amp; Publish Validation</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-06-integrations-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-06-integrations-v1</id>
    <published>2026-11-06T00:00:00Z</published>
    <updated>2026-11-06T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Integration Services" />
    <category term="Application Integration" />
    <category term="integrations.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] BigQuery: Dataset Replication, Python UDFs, and Breaking Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-06-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-06-bigquery-v2</id>
    <published>2026-11-06T00:00:00Z</published>
    <updated>2026-11-06T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI v1beta1: Major Breaking Changes, GenAI Expansion, and Feature Re-rollouts</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-06-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-06-aiplatform-v1beta1</id>
    <published>2026-11-06T00:00:00Z</published>
    <updated>2026-11-06T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: Agent Identity, Memory, Notebook Defaults, and API Rollbacks</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-06-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-06-aiplatform-v1</id>
    <published>2026-11-06T00:00:00Z</published>
    <updated>2026-11-06T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>YouTube Shorts Thumbnails Now Available</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-05-youtube-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-05-youtube-v3</id>
    <published>2026-11-05T00:00:00Z</published>
    <updated>2026-11-05T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="YouTube Data API" />
    <category term="youtube.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] BigQuery Reservation Adds Edition Upgrade API</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-05-bigqueryreservation-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-05-bigqueryreservation-v1</id>
    <published>2026-11-05T00:00:00Z</published>
    <updated>2026-11-05T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Reservation" />
    <category term="bigqueryreservation.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking Changes: Read-Only Fields; New Feature Toggles &amp; OAuth Scopes</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-03-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-03-discoveryengine-v1beta</id>
    <published>2026-11-03T00:00:00Z</published>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: Feature Toggle Controls &amp; Breaking Schema Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-03-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-03-discoveryengine-v1alpha</id>
    <published>2026-11-03T00:00:00Z</published>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking Change: Many Fields Now Read-Only; New Feature Controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-03-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-03-discoveryengine-v1</id>
    <published>2026-11-03T00:00:00Z</published>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataform: Async Workspace Creation &amp; Concurrency Control</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-03-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-03-dataform-v1beta1</id>
    <published>2026-11-03T00:00:00Z</published>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>Dataform Workflows Get Concurrency Control</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-03-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-03-dataform-v1</id>
    <published>2026-11-03T00:00:00Z</published>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
  <entry>
    <title>AlloyDB Autoscaling Adds Connection Count Metric</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-02-alloydb-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-02-alloydb-v1</id>
    <published>2026-11-02T00:00:00Z</published>
    <updated>2026-11-02T00:00:00Z</updated>
    <summary type="text">AlloyDB&apos;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.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1" />
  </entry>
  <entry>
    <title>AlloyDB Autoscaling Gains Connection Count Policy</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-01-alloydb-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-01-alloydb-v1beta</id>
    <published>2026-11-01T00:00:00Z</published>
    <updated>2026-11-01T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1beta" />
  </entry>
  <entry>
    <title>AlloyDB Autoscaling Now Supports Connection Count Policies</title>
    <link href="https://google-cloud-radar.com/changes/2026-11-01-alloydb-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-11-01-alloydb-v1alpha</id>
    <published>2026-11-01T00:00:00Z</published>
    <updated>2026-11-01T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1alpha" />
  </entry>
  <entry>
    <title>New DATA_LAYER Error Code for CRM Logs</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-31-integrations-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-31-integrations-v1</id>
    <published>2026-10-31T00:00:00Z</published>
    <updated>2026-10-31T00:00:00Z</updated>
    <summary type="text">The `CrmlogErrorCode` schema in Application Integration now includes a new `DATA_LAYER` enum value for `commonErrorCode`. This expands the set of identifiable error types for CRM log entries.</summary>
    <category term="Integration Services" />
    <category term="Application Integration" />
    <category term="integrations.v1" />
  </entry>
  <entry>
    <title>BigQuery Data Policy: Advanced Matching Conditions</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-31-bigquerydatapolicy-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-31-bigquerydatapolicy-v2</id>
    <published>2026-10-31T00:00:00Z</published>
    <updated>2026-10-31T00:00:00Z</updated>
    <summary type="text">The BigQuery Data Policy API now supports a new `matchingCondition` property within the `DataPolicy` resource. This allows developers to define data policies using SQL expressions, enabling more dynamic and fine-grained control based on column tags.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Data Policy" />
    <category term="bigquerydatapolicy.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Workload Capture/Replay Request Schemas Renamed</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-30-sqladmin-v1beta4" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-30-sqladmin-v1beta4</id>
    <published>2026-10-30T00:00:00Z</published>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary type="text">The request body schemas for Cloud SQL Admin API&apos;s workload capture and replay methods have been renamed, requiring updates to client code.</summary>
    <category term="Databases" />
    <category term="Cloud SQL" />
    <category term="sqladmin.v1beta4" />
  </entry>
  <entry>
    <title>Dataproc Adds Advanced Cluster Scheduling Controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-30-dataproc-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-30-dataproc-v1</id>
    <published>2026-10-30T00:00:00Z</published>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary type="text">Dataproc clusters can now be configured with a `SchedulingConfig` to define resource allocation behavior. This new feature allows specifying a `requestedRunDuration` for cluster lifetime and a `schedulingTimeout` for resource provisioning.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Dataproc" />
    <category term="dataproc.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataplex: Data Product Insights &amp; Critical Schema Immutability</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-30-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-30-dataplex-v1</id>
    <published>2026-10-30T00:00:00Z</published>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary type="text">Dataplex now generates rich data product insights, including asset descriptions and sample queries. Be aware of critical breaking changes as several key documentation and entry properties are now read-only, requiring immediate code updates.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AI Platform v1beta1: Major Breaking Changes &amp; New File/Embedding APIs</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-30-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-30-aiplatform-v1beta1</id>
    <published>2026-10-30T00:00:00Z</published>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary type="text">This update brings significant breaking changes, including the removal of `evaluationTasks.operations` and a rollback of `continuationToken` in `GenaiVertexV1beta1Interaction`. Developers must update their code. On the feature side, new file management and batch embedding capabilities are now available, alongside enhancements to video generation.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: Breaking Changes &amp; New File/Batch Embedding APIs</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-30-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-30-aiplatform-v1</id>
    <published>2026-10-30T00:00:00Z</published>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary type="text">This update introduces several breaking changes by making key parameters strictly required and certain schema properties read-only. Developers also gain significant new file management capabilities for publisher models and a new batch embedding method.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Workload Capture Request Schemas Renamed (Breaking)</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-28-sqladmin-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-28-sqladmin-v1</id>
    <published>2026-10-28T00:00:00Z</published>
    <updated>2026-10-28T00:00:00Z</updated>
    <summary type="text">The request body schemas for Cloud SQL&apos;s Workload Capture methods (start, startReplay, stop, stopReplay) have been renamed. This is a breaking change requiring updates to client code.</summary>
    <category term="Databases" />
    <category term="Cloud SQL" />
    <category term="sqladmin.v1" />
  </entry>
  <entry>
    <title>Looker Exports Get ESA Migration Token</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-28-looker-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-28-looker-v1</id>
    <published>2026-10-28T00:00:00Z</published>
    <updated>2026-10-28T00:00:00Z</updated>
    <summary type="text">The `ExportMetadata` schema now includes an `esaMigrationToken` field, providing an opaque capability token for O2C Elite System Activity (ESA) direct dataset migrations. This enhances the secure handling of cloned source datasets during import.</summary>
    <category term="Data Analytics" />
    <category term="Looker Core" />
    <category term="looker.v1" />
  </entry>
  <entry>
    <title>Refined OAuth Scopes for Transfer Config Management</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-25-bigquerydatatransfer-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-25-bigquerydatatransfer-v1</id>
    <published>2026-10-25T00:00:00Z</published>
    <updated>2026-10-25T00:00:00Z</updated>
    <summary type="text">The BigQuery Data Transfer Service now recommends more granular `bigquery` OAuth scopes for creating and patching transfer configurations. The broader `cloud-platform` scope remains supported as an alternative.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Data Transfer Service" />
    <category term="bigquerydatatransfer.v1" />
  </entry>
  <entry>
    <title>ImageVersion now indicates Development Mode support</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-24-composer-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-24-composer-v1beta1</id>
    <published>2026-10-24T00:00:00Z</published>
    <updated>2026-10-24T00:00:00Z</updated>
    <summary type="text">The `ImageVersion` schema in Cloud Composer now includes a `devModeSupported` boolean property. This allows developers to programmatically check if a specific image version supports creating environments in `DEVELOPMENT` mode.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Composer" />
    <category term="composer.v1beta1" />
  </entry>
  <entry>
    <title>Composer ImageVersion now indicates dev mode support</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-24-composer-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-24-composer-v1</id>
    <published>2026-10-24T00:00:00Z</published>
    <updated>2026-10-24T00:00:00Z</updated>
    <summary type="text">The `ImageVersion` schema in Cloud Composer now includes a `devModeSupported` boolean property. This new field indicates whether a specific image version can be used to create environments in `DEVELOPMENT` mode.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Composer" />
    <category term="composer.v1" />
  </entry>
  <entry>
    <title>Enhanced Feedback &amp; Tool Visibility Controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-23-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-23-discoveryengine-v1beta</id>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary type="text">Discovery Engine now offers more granular feedback options, including specific reasons for positive responses and a dedicated structure for disputing Model Armor verdicts. New schemas also hint at future fine-grained control over tool visibility.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>Enhanced Feedback &amp; Tool Visibility Controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-23-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-23-discoveryengine-v1alpha</id>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary type="text">Discovery Engine now supports detailed feedback on Model Armor verdicts and response quality. New schemas also introduce fine-grained visibility controls for internal tools and allow specifying Identity Provider configurations during project provisioning.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>Discovery Engine: Model Armor Dispute Feedback &amp; Granular User Signals</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-23-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-23-discoveryengine-v1</id>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary type="text">Discovery Engine now allows developers to capture detailed user disputes for Model Armor verdicts, enabling better refinement of AI safety features. Additionally, new positive feedback reasons provide more nuanced insights into user satisfaction.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataform Adds Async Compilation, Clarifies Parent Requirement</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-23-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-23-dataform-v1beta1</id>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary type="text">Dataform now offers an asynchronous method to create compilation results. While marked as a breaking change, this primarily defines the required `parent` parameter for the *new* `createLongRunning` method, ensuring proper resource scoping from the start.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] New Async Compilation Method in Dataform</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-23-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-23-dataform-v1</id>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
    <summary type="text">Dataform now offers a new asynchronous method, `createLongRunning`, for creating compilation results, returning an `Operation` for tracking. This method requires a `parent` parameter.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
  <entry>
    <title>Data Lineage `runs.list` Method Gains New Scopes</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-22-datalineage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-22-datalineage-v1</id>
    <published>2026-10-22T00:00:00Z</published>
    <updated>2026-10-22T00:00:00Z</updated>
    <summary type="text">The `projects.locations.processes.runs.list` method in the Data Lineage API now supports dedicated `datalineage.read-write` and `datalineage.readonly` OAuth scopes. This provides more granular permission control for listing lineage runs.</summary>
    <category term="Data Analytics" />
    <category term="Data Lineage" />
    <category term="datalineage.v1" />
  </entry>
  <entry>
    <title>Filter Dataflow Jobs by Creation and Termination Time</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-22-dataflow-v1b3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-22-dataflow-v1b3</id>
    <published>2026-10-22T00:00:00Z</published>
    <updated>2026-10-22T00:00:00Z</updated>
    <summary type="text">The Dataflow API now supports filtering job listings by creation and termination time ranges. This enhancement applies to both aggregated and location-specific job list methods, providing more granular control over job visibility.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Dataflow" />
    <category term="dataflow.v1b3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AlloyDB Exposes CA &amp; Network Info (Read-Only)</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-22-alloydb-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-22-alloydb-v1beta</id>
    <published>2026-10-22T00:00:00Z</published>
    <updated>2026-10-22T00:00:00Z</updated>
    <summary type="text">AlloyDB v1beta now exposes cluster Certificate Authority (CA) details and instance network information as read-only properties. Developers should note that several new fields, including CA certificates and instance network details, are now explicitly output-only, which is a breaking change if you were attempting to set them.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AlloyDB: CA Certs &amp; Public DNS Info, Breaking Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-22-alloydb-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-22-alloydb-v1alpha</id>
    <published>2026-10-22T00:00:00Z</published>
    <updated>2026-10-22T00:00:00Z</updated>
    <summary type="text">AlloyDB now provides crucial CA certificate information for secure PostgreSQL connections and public DNS names for instances. A new `publicDnsEnabled` option allows configuring public DNS. Be aware of breaking changes as `rootCaCert`, `certificateAuthorityInfo`, `networkInfo`, and `publicDnsName` are now read-only.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking: Custom Domains &amp; Instances Get Read-Only Fields; New Export Timestamp for ESA</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-21-looker-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-21-looker-v1</id>
    <published>2026-10-21T00:00:00Z</published>
    <updated>2026-10-21T00:00:00Z</updated>
    <summary type="text">The `CustomDomain.state` and `Instance.maintenanceSchedule` properties are now read-only, which is a breaking change for any automation modifying them. Additionally, `ExportMetadata` gains a new `exportTime` field to track Elite System Activity (ESA) BigQuery dataset migrations.</summary>
    <category term="Data Analytics" />
    <category term="Looker Core" />
    <category term="looker.v1" />
  </entry>
  <entry>
    <title>Dataplex Data Docs Get Custom Instructions</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-21-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-21-dataplex-v1</id>
    <published>2026-10-21T00:00:00Z</published>
    <updated>2026-10-21T00:00:00Z</updated>
    <summary type="text">Dataplex now allows developers to provide custom instructions when generating data documentation. This new optional field offers more control over the documentation process.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>In-App Product Subscriptions Deprecated</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-20-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-20-androidpublisher-v3</id>
    <published>2026-10-20T00:00:00Z</published>
    <updated>2026-10-20T00:00:00Z</updated>
    <summary type="text">The `InAppProduct` resource in the Android Publisher API is deprecating subscription-related fields and the subscription `purchaseType`. Developers should now use the dedicated Subscriptions API for managing subscriptions.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Cloud SQL `stopReplay` Method Breaking Change</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-18-sqladmin-v1beta4" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-18-sqladmin-v1beta4</id>
    <published>2026-10-18T00:00:00Z</published>
    <updated>2026-10-18T00:00:00Z</updated>
    <summary type="text">The `workloadCaptures.stopReplay` method has undergone a breaking change, removing the `workloadId` parameter from its URI path and altering the `StopWorkloadReplayContext` schema. This is a significant adjustment to the recently introduced workload replay functionality.</summary>
    <category term="Databases" />
    <category term="Cloud SQL" />
    <category term="sqladmin.v1beta4" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Cloud SQL Admin: Workload Replay Stop Method Refactored</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-17-sqladmin-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-17-sqladmin-v1</id>
    <published>2026-10-17T00:00:00Z</published>
    <updated>2026-10-17T00:00:00Z</updated>
    <summary type="text">The `workloadCaptures.stopReplay` method has undergone a breaking refactor. The `workloadId` path parameter is removed, and the `StopWorkloadReplayContext` schema no longer includes `replayInstance` or `workloadId` properties. This requires immediate code updates.</summary>
    <category term="Databases" />
    <category term="Cloud SQL" />
    <category term="sqladmin.v1" />
  </entry>
  <entry>
    <title>Secure Context for Extract Jobs</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-17-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-17-bigquery-v2</id>
    <published>2026-10-17T00:00:00Z</published>
    <updated>2026-10-17T00:00:00Z</updated>
    <summary type="text">BigQuery&apos;s `secureContext` feature, previously available for queries, now extends to extract jobs. This allows passing sensitive, context-specific information to modify extract job behavior.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: Generation Continuation &amp; Breaking Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-17-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-17-aiplatform-v1beta1</id>
    <published>2026-10-17T00:00:00Z</published>
    <updated>2026-10-17T00:00:00Z</updated>
    <summary type="text">This Vertex AI v1beta1 update introduces significant breaking changes, making several properties read-only and altering a schema type. On the feature front, you can now resume long-running content generation with new continuation tokens and access detailed content metadata, including citations and grounding sources.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking Changes &amp; Major Interaction API Expansion!</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-17-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-17-aiplatform-v1</id>
    <published>2026-10-17T00:00:00Z</published>
    <updated>2026-10-17T00:00:00Z</updated>
    <summary type="text">This update introduces significant breaking changes by making several core parameters strictly required and numerous `GenaiVertexV1Interaction` properties read-only. On the feature front, a massive expansion of the `interactions` API enables advanced streaming, tool use (like code execution, file search, Google Maps/Search), and rich content handling for generative AI applications.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Composer: Environment Rollback Targets Exposed</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-15-composer-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-15-composer-v1beta1</id>
    <published>2026-10-15T00:00:00Z</published>
    <updated>2026-10-15T00:00:00Z</updated>
    <summary type="text">Cloud Composer environments now expose `imageVersionRollbackTargets` within `SoftwareConfig`, providing visibility into which image versions an environment can be rolled back to. These new fields are output-only; attempting to set them will now result in an error.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Composer" />
    <category term="composer.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Composer Environment Rollback Targets</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-15-composer-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-15-composer-v1</id>
    <published>2026-10-15T00:00:00Z</published>
    <updated>2026-10-15T00:00:00Z</updated>
    <summary type="text">Cloud Composer environments now expose `imageVersionRollbackTargets` in `SoftwareConfig`, providing insights into available rollback points and their last active usage.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Composer" />
    <category term="composer.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking: Channel Management Removed</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-14-storage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-14-storage-v1</id>
    <published>2026-10-14T00:00:00Z</published>
    <updated>2026-10-14T00:00:00Z</updated>
    <summary type="text">The `channels.stop` method and the `Channel` schema have been completely removed from the Cloud Storage API. This is a breaking change affecting push notification channel management.</summary>
    <category term="Storage" />
    <category term="Cloud Storage" />
    <category term="storage.v1" />
  </entry>
  <entry>
    <title>Drive API: Approval Schema Read-Only Flags Removed</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-14-drive-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-14-drive-v3</id>
    <published>2026-10-14T00:00:00Z</published>
    <updated>2026-10-14T00:00:00Z</updated>
    <summary type="text">The `Approval` schema in the Drive API no longer explicitly marks `completeTime`, `createTime`, `modifyTime`, `fileContentChangeBehavior`, and `status` properties as read-only in its discovery document. This is a metadata update.</summary>
    <category term="Data Analytics" />
    <category term="Google Drive API" />
    <category term="drive.v3" />
  </entry>
  <entry>
    <title>Discovery Engine: Notebook Search Scoping &amp; Feedback Detail</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-14-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-14-discoveryengine-v1beta</id>
    <published>2026-10-14T00:00:00Z</published>
    <updated>2026-10-14T00:00:00Z</updated>
    <summary type="text">Discovery Engine now offers granular control over federated searches by allowing you to restrict data stores to specific notebooks. Additionally, new options for partial and prefix field matching are available, and conversational feedback can now include more detailed context like step sequence numbers and trajectory IDs.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: Rollbacks for ToolCall &amp; Collaborative KnowledgeSpace Ops, New Private OAuth &amp; Notebook Scoping</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-14-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-14-discoveryengine-v1alpha</id>
    <published>2026-10-14T00:00:00Z</published>
    <updated>2026-10-14T00:00:00Z</updated>
    <summary type="text">This update includes significant breaking changes: the recently added `toolCalls.operations.get` and `collaborativeProjects.knowledgeSpaces.operations.get` methods have been removed. Developers should update their integrations. New features include private network OAuth configuration, notebook-level data store scoping, and enhanced field matching options.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>Discovery Engine: Notebook Scoping, Field Matching, &amp; Feedback Enhancements</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-14-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-14-discoveryengine-v1</id>
    <published>2026-10-14T00:00:00Z</published>
    <updated>2026-10-14T00:00:00Z</updated>
    <summary type="text">Discovery Engine gains new capabilities for federated search data stores, allowing restriction to specific notebooks. Developers can now configure partial and prefix matching for fields, and feedback tracking gets more granular with new conversation info.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>Dataproc Introduces Flexible Instance Groups for HO Clusters</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-14-dataproc-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-14-dataproc-v1</id>
    <published>2026-10-14T00:00:00Z</published>
    <updated>2026-10-14T00:00:00Z</updated>
    <summary type="text">Dataproc now supports High Obtainability (HO) flexible instance groups, offering a new, more resilient way to configure clusters. This includes a new `FlexibleInstanceGroupConfig` schema for detailed control over master, worker, and secondary worker instances.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Dataproc" />
    <category term="dataproc.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataplex: Batch Metadata &amp; Change Requests</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-14-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-14-dataplex-v1</id>
    <published>2026-10-14T00:00:00Z</published>
    <updated>2026-10-14T00:00:00Z</updated>
    <summary type="text">Dataplex introduces powerful new batch operations for managing metadata within EntryGroups, allowing direct updates or formal change requests. Developers should be aware of a breaking change: the `batchChangeMetadataResponse` property in `GoogleCloudDataplexV1ChangeRequest` is now read-only.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>Filter Lineage Search by Project</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-14-datalineage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-14-datalineage-v1</id>
    <published>2026-10-14T00:00:00Z</published>
    <updated>2026-10-14T00:00:00Z</updated>
    <summary type="text">The Data Lineage API now allows developers to filter `searchLineageStreaming` results by specific projects, enabling more targeted and efficient lineage queries.</summary>
    <category term="Data Analytics" />
    <category term="Data Lineage" />
    <category term="datalineage.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Cloud SQL: Precheck Options, Database Center &amp; Workload Capture Updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-13-sqladmin-v1beta4" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-13-sqladmin-v1beta4</id>
    <published>2026-10-13T00:00:00Z</published>
    <updated>2026-10-13T00:00:00Z</updated>
    <summary type="text">Cloud SQL introduces new controls for major version upgrades and Database Center integration. The `WorkloadCapture` schema also sees updates, including a new `TERMINATED` state and a breaking change where `backupId` is now read-only.</summary>
    <category term="Databases" />
    <category term="Cloud SQL" />
    <category term="sqladmin.v1beta4" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataform Workspaces Gain Commit History Access</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-13-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-13-dataform-v1beta1</id>
    <published>2026-10-13T00:00:00Z</published>
    <updated>2026-10-13T00:00:00Z</updated>
    <summary type="text">Dataform now allows developers to programmatically fetch the commit history of a workspace, enhancing Git integration. A new field for personal authentication in Git remote settings is also available.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AlloyDB: &apos;edition&apos; Deprecated, &apos;expressConfig&apos; Read-Only</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-13-alloydb-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-13-alloydb-v1beta</id>
    <published>2026-10-13T00:00:00Z</published>
    <updated>2026-10-13T00:00:00Z</updated>
    <summary type="text">The recently introduced `edition` field on AlloyDB `Cluster` and `Backup` schemas is now deprecated. Developers should transition to using the new `expressConfig` property on `Backup` for Express cluster details, which is output-only and considered a breaking change if you anticipated setting it.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AlloyDB: `edition` deprecated, `Backup.expressConfig` now output-only</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-13-alloydb-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-13-alloydb-v1alpha</id>
    <published>2026-10-13T00:00:00Z</published>
    <updated>2026-10-13T00:00:00Z</updated>
    <summary type="text">The `edition` field on both `Backup` and `Cluster` resources is now deprecated, with a recommendation to use the `ExpressConfig` property instead. Additionally, the `expressConfig` property on `Backup` has been made read-only, which is a breaking change if you were previously setting it.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1alpha" />
  </entry>
  <entry>
    <title>AlloyDB Read Pool Autoscaling Arrives</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-13-alloydb-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-13-alloydb-v1</id>
    <published>2026-10-13T00:00:00Z</published>
    <updated>2026-10-13T00:00:00Z</updated>
    <summary type="text">AlloyDB now supports autoscaling for read pools, allowing you to dynamically adjust the number of read replica nodes based on CPU utilization or predefined schedules. This significantly simplifies managing read capacity and optimizing costs.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Cloud SQL: Workload Capture `backupId` Read-Only; New Instance Controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-09-sqladmin-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-09-sqladmin-v1</id>
    <published>2026-10-09T00:00:00Z</published>
    <updated>2026-10-09T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="Cloud SQL" />
    <category term="sqladmin.v1" />
  </entry>
  <entry>
    <title>Vertex AI: LoRA &amp; Super Res for Video, Agent Model Config</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-09-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-09-aiplatform-v1beta1</id>
    <published>2026-10-09T00:00:00Z</published>
    <updated>2026-10-09T00:00:00Z</updated>
    <summary type="text">Vertex AI&apos;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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Advanced Video Gen &amp; Agent Model Control</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-09-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-09-aiplatform-v1</id>
    <published>2026-10-09T00:00:00Z</published>
    <updated>2026-10-09T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Test Unpublished Integration Drafts</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-integrations-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-integrations-v2</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">The `PostToQueueWithTriggerIdRequest` schema now includes a `workflowId` field, allowing you to target specific, even unpublished, versions of your integrations for testing.</summary>
    <category term="Integration Services" />
    <category term="Application Integration" />
    <category term="integrations.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking Change &amp; Enhanced Testing for Integrations</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-integrations-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-integrations-v1</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Integration Services" />
    <category term="Application Integration" />
    <category term="integrations.v1" />
  </entry>
  <entry>
    <title>Discovery Engine: Link Feedback to Agent Tasks</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-discoveryengine-v1beta</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking: Widget Config &amp; ToolCall Ops</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-discoveryengine-v1alpha</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: `autoModelId` Now Output-Only; Sobi Task Tracking Added</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-discoveryengine-v1</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataplex removes Unstructured Data Profiling</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-dataplex-v1</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] BigLake Views Gain IAM, &apos;resource&apos; Parameter Now Required</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-08-biglake-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-08-biglake-v1</id>
    <published>2026-10-08T00:00:00Z</published>
    <updated>2026-10-08T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="BigLake" />
    <category term="biglake.v1" />
  </entry>
  <entry>
    <title>Looker Instances Expose Authentication Types</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-06-looker-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-06-looker-v1</id>
    <published>2026-10-06T00:00:00Z</published>
    <updated>2026-10-06T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Looker Core" />
    <category term="looker.v1" />
  </entry>
  <entry>
    <title>Cloud Storage: New Hard Delete Pause for Soft-Deleted Objects</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-03-storage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-03-storage-v1</id>
    <published>2026-10-03T00:00:00Z</published>
    <updated>2026-10-03T00:00:00Z</updated>
    <summary type="text">Cloud Storage buckets now support a &apos;hard delete pause&apos; 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.</summary>
    <category term="Storage" />
    <category term="Cloud Storage" />
    <category term="storage.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: Custom Voices, Cache Control, and Breaking Schema Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-03-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-03-aiplatform-v1beta1</id>
    <published>2026-10-03T00:00:00Z</published>
    <updated>2026-10-03T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: New Serving Profiles, Breaking Changes &amp; Scope Updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-03-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-03-aiplatform-v1</id>
    <published>2026-10-03T00:00:00Z</published>
    <updated>2026-10-03T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Granular IAM for Dataplex Agent Tasks</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-02-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-02-dataplex-v1</id>
    <published>2026-10-02T00:00:00Z</published>
    <updated>2026-10-02T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AlloyDB Express Clusters &amp; Breaking Observability Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-02-alloydb-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-02-alloydb-v1beta</id>
    <published>2026-10-02T00:00:00Z</published>
    <updated>2026-10-02T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AlloyDB Express Clusters &amp; Observability Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-02-alloydb-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-02-alloydb-v1alpha</id>
    <published>2026-10-02T00:00:00Z</published>
    <updated>2026-10-02T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking: AlloyDB Instance Observability &amp; Query Insights Properties Are Now Read-Only</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-02-alloydb-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-02-alloydb-v1</id>
    <published>2026-10-02T00:00:00Z</published>
    <updated>2026-10-02T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] YouTube Comments: `imageUrl` Now Output-Only</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-01-youtube-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-01-youtube-v3</id>
    <published>2026-10-01T00:00:00Z</published>
    <updated>2026-10-01T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="YouTube Data API" />
    <category term="youtube.v3" />
  </entry>
  <entry>
    <title>Automate SQL Server DDL Handling</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-01-datastream-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-01-datastream-v1</id>
    <published>2026-10-01T00:00:00Z</published>
    <updated>2026-10-01T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Datastream" />
    <category term="datastream.v1" />
  </entry>
  <entry>
    <title>Gemini Notebook Audit Logs Now Available</title>
    <link href="https://google-cloud-radar.com/changes/2026-10-01-admin-reports-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-10-01-admin-reports-v1</id>
    <published>2026-10-01T00:00:00Z</published>
    <updated>2026-10-01T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Admin SDK" />
    <category term="admin.reports_v1" />
  </entry>
  <entry>
    <title>Pub/Sub Bigtable Sink: Custom Row Keys &amp; Columns</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-30-pubsub-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-30-pubsub-v1</id>
    <published>2026-09-30T00:00:00Z</published>
    <updated>2026-09-30T00:00:00Z</updated>
    <summary type="text">The Pub/Sub Bigtable integration now offers significantly enhanced control over data ingestion. Developers can define custom row keys and map message fields to specific Bigtable column families, moving beyond the default fixed schema.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Pub/Sub" />
    <category term="pubsub.v1" />
  </entry>
  <entry>
    <title>Cross-Cloud Caching for External Connections</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-30-bigqueryconnection-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-30-bigqueryconnection-v1</id>
    <published>2026-09-30T00:00:00Z</published>
    <updated>2026-09-30T00:00:00Z</updated>
    <summary type="text">BigQuery connections to AWS, Azure, and Salesforce Data Cloud now support an optional cross-cloud caching feature. This can improve query performance and reduce network egress costs for external data sources.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Connection API" />
    <category term="bigqueryconnection.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataproc: Multi-Zone Clusters &amp; Read-Only Field Updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-29-dataproc-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-29-dataproc-v1</id>
    <published>2026-09-29T00:00:00Z</published>
    <updated>2026-09-29T00:00:00Z</updated>
    <summary type="text">Dataproc now supports multi-zone cluster configurations, enhancing resilience and availability. This release also includes breaking changes, making several fields in `ApplicationAttemptInfo` and `VirtualClusterOperationMetadata` read-only.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Dataproc" />
    <category term="dataproc.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Introducing Spend Caps for Billing Budgets</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-29-billingbudgets-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-29-billingbudgets-v1</id>
    <published>2026-09-29T00:00:00Z</published>
    <updated>2026-09-29T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="FinOps &amp; Billing" />
    <category term="Cloud Billing Budgets" />
    <category term="billingbudgets.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] New Object Context API &amp; Breaking Changes Clarified</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-28-storage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-28-storage-v1</id>
    <published>2026-09-28T00:00:00Z</published>
    <updated>2026-09-28T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Storage" />
    <category term="Cloud Storage" />
    <category term="storage.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] BigQuery: Secure Query Context, Native Parquet Geography Export, and a Breaking Change</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-26-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-26-bigquery-v2</id>
    <published>2026-09-26T00:00:00Z</published>
    <updated>2026-09-26T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking Change: AssistAnswer&apos;s `connectorDisplayNames` is now Read-Only</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-25-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-25-discoveryengine-v1beta</id>
    <published>2026-09-25T00:00:00Z</published>
    <updated>2026-09-25T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: AssistAnswer Field Now Read-Only, New OAuth Auth Option</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-25-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-25-discoveryengine-v1alpha</id>
    <published>2026-09-25T00:00:00Z</published>
    <updated>2026-09-25T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: AssistAnswer `connectorDisplayNames` is now read-only</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-25-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-25-discoveryengine-v1</id>
    <published>2026-09-25T00:00:00Z</published>
    <updated>2026-09-25T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>AlloyDB: `trackActiveQueryPlan` Deprecated</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-25-alloydb-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-25-alloydb-v1beta</id>
    <published>2026-09-25T00:00:00Z</published>
    <updated>2026-09-25T00:00:00Z</updated>
    <summary type="text">The `trackActiveQueryPlan` property within AlloyDB&apos;s `ObservabilityInstanceConfig` schema has been deprecated. Developers should plan to migrate away from using this feature.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1beta" />
  </entry>
  <entry>
    <title>AlloyDB: Observability Config Field Deprecated</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-25-alloydb-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-25-alloydb-v1alpha</id>
    <published>2026-09-25T00:00:00Z</published>
    <updated>2026-09-25T00:00:00Z</updated>
    <summary type="text">The `trackActiveQueryPlan` field within the `ObservabilityInstanceConfig` schema has been marked as deprecated. Developers should update their configurations to avoid using this field.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1alpha" />
  </entry>
  <entry>
    <title>AlloyDB Enhances IAM Group Authentication</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-25-alloydb-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-25-alloydb-v1</id>
    <published>2026-09-25T00:00:00Z</published>
    <updated>2026-09-25T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] YouTube Data API: `postId` Removed, `favorite`/`like` Activities Gone, `subscription` Restored</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-24-youtube-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-24-youtube-v3</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="YouTube Data API" />
    <category term="youtube.v3" />
  </entry>
  <entry>
    <title>Drive API clarifies concurrent permission warnings</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-24-drive-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-24-drive-v3</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <summary type="text">The Google Drive API&apos;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.</summary>
    <category term="Data Analytics" />
    <category term="Google Drive API" />
    <category term="drive.v3" />
  </entry>
  <entry>
    <title>Permission Concurrency Warning Clarified</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-24-drive-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-24-drive-v2</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <summary type="text">The Google Drive API&apos;s permission methods (`delete`, `insert`, `patch`, `update`) now feature updated descriptions that clarify the scope of concurrent modification warnings.</summary>
    <category term="Data Analytics" />
    <category term="Google Drive API" />
    <category term="drive.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Major Breaking Changes: Data Taxonomy &amp; Attributes Removed</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-24-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-24-dataplex-v1</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>Increased Deobfuscation File Upload Limit</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-24-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-24-androidpublisher-v3</id>
    <published>2026-09-24T00:00:00Z</published>
    <updated>2026-09-24T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>Client Telemetry for Pub/Sub Publish Operations</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-pubsub-v1beta2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-pubsub-v1beta2</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Pub/Sub" />
    <category term="pubsub.v1beta2" />
  </entry>
  <entry>
    <title>Pub/Sub Adds Client Telemetry for Publish Operations</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-pubsub-v1beta1a" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-pubsub-v1beta1a</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Pub/Sub" />
    <category term="pubsub.v1beta1a" />
  </entry>
  <entry>
    <title>Pub/Sub Adds Client Telemetry for Publish Operations</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-pubsub-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-pubsub-v1</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">New `PubsubClientTelemetry` and `PublishOperation` schemas provide client-side debugging information for publish calls, including hedging attempts and start times.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Pub/Sub" />
    <category term="pubsub.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Lakehouse Proxy Config Introduced (Breaking)</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-metastore-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-metastore-v1beta</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Metastore v1alpha: Lakehouse Proxy Config &amp; Read-Only Fields</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-metastore-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-metastore-v1alpha</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">The Metastore v1alpha API introduces Lakehouse proxy configuration for phased namespace migrations. The new &apos;lakehouseProxyConfig&apos; field in the Service schema and its sub-properties are now explicitly read-only, which is a breaking change.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Lakehouse Proxy Routing &amp; Read-Only Config</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-metastore-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-metastore-v1</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine v1beta: License Configuration &amp; Schema Doc Updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-discoveryengine-v1beta</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">Adds BillingAccountLicenseConfig schema properties and refines parameter documentation for suggestions, searches, and user events.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine v1alpha: Knowledge Spaces Operations &amp; Sharing Config</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-discoveryengine-v1alpha</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">Introduces operations get method for collaborative project knowledge spaces, updates agent sharing configuration scopes, and adds widget and billing license properties.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Discovery Engine: Widget Config Component Tag &amp; License Config Updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-discoveryengine-v1</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">Updates Discovery Engine v1 schemas, introducing read-only tag properties to WidgetConfigCollectionComponent and adding BillingAccountLicenseConfig.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>Dataform: File path description clarified</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-22-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-22-dataform-v1</id>
    <published>2026-09-22T00:00:00Z</published>
    <updated>2026-09-22T00:00:00Z</updated>
    <summary type="text">A minor documentation update clarifies the reference point for file paths within Dataform workspaces. No functional changes or developer action required.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
  <entry>
    <title>New `updateId` for Hosted App Responses</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-22-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-22-androidpublisher-v3</id>
    <published>2026-09-22T00:00:00Z</published>
    <updated>2026-09-22T00:00:00Z</updated>
    <summary type="text">The `UpdateAppStoreHostedAppResponse` now includes an `updateId` to uniquely identify and track specific versions of hosted app updates, enabling correlation with publishing signals.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>Analytics Hub: Custom Bigtable Row Keys &amp; Column Mappings</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-22-analyticshub-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-22-analyticshub-v1</id>
    <published>2026-09-22T00:00:00Z</published>
    <updated>2026-09-22T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Analytics Hub" />
    <category term="analyticshub.v1" />
  </entry>
  <entry>
    <title>Detailed Export Telemetry and Self-Hosted Source Support</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-19-looker-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-19-looker-v1</id>
    <published>2026-09-19T00:00:00Z</published>
    <updated>2026-09-19T00:00:00Z</updated>
    <summary type="text">Looker&apos;s export process now provides granular telemetry via new ExportMetrics and ComponentMetrics schemas, alongside support for self-hosted instance sources.</summary>
    <category term="Data Analytics" />
    <category term="Looker Core" />
    <category term="looker.v1" />
  </entry>
  <entry>
    <title>Dataplex adds LLM token tracking for Data Documentation</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-19-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-19-dataplex-v1</id>
    <published>2026-09-19T00:00:00Z</published>
    <updated>2026-09-19T00:00:00Z</updated>
    <summary type="text">Dataplex now provides granular observability for LLM-powered data documentation scans, including detailed token usage and compute unit consumption.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Agent Patching goes Async and Video &apos;Pro Edit&apos; arrives</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-19-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-19-aiplatform-v1beta1</id>
    <published>2026-09-19T00:00:00Z</published>
    <updated>2026-09-19T00:00:00Z</updated>
    <summary type="text">Vertex AI v1beta1 shifts Agent updates to Long Running Operations and introduces experimental &apos;Pro Edit&apos; video capabilities. New observability features and Reasoning Engine garbage collection also debut.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI adds Video &apos;Pro Edit&apos; and Agent Observability</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-19-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-19-aiplatform-v1</id>
    <published>2026-09-19T00:00:00Z</published>
    <updated>2026-09-19T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AlloyDB adds Postgres 19 support and Cluster Editions</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-18-alloydb-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-18-alloydb-v1beta</id>
    <published>2026-09-18T00:00:00Z</published>
    <updated>2026-09-18T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] AlloyDB adds Postgres 19 support and Cluster Editions</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-18-alloydb-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-18-alloydb-v1alpha</id>
    <published>2026-09-18T00:00:00Z</published>
    <updated>2026-09-18T00:00:00Z</updated>
    <summary type="text">AlloyDB v1alpha introduces support for Postgres 19 and a new edition classification for clusters, while making the edition field read-only on backups.</summary>
    <category term="Databases" />
    <category term="AlloyDB" />
    <category term="alloydb.v1alpha" />
  </entry>
  <entry>
    <title>Clarified Unmanaged Account Resolution Logic</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-18-admin-directory-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-18-admin-directory-v1</id>
    <published>2026-09-18T00:00:00Z</published>
    <updated>2026-09-18T00:00:00Z</updated>
    <summary type="text">The Directory API documentation now explicitly details the HTTP response codes returned when resolving unmanaged user account conflicts during user creation.</summary>
    <category term="Data Analytics" />
    <category term="Admin SDK" />
    <category term="admin.directory_v1" />
  </entry>
  <entry>
    <title>Granular IAM Filtering and Search-As-You-Type Tuning</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-17-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-17-discoveryengine-v1beta</id>
    <published>2026-09-17T00:00:00Z</published>
    <updated>2026-09-17T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Gemini Access Controls and Search-As-You-Type Tuning</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-17-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-17-discoveryengine-v1alpha</id>
    <published>2026-09-17T00:00:00Z</published>
    <updated>2026-09-17T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Search-as-you-type tuning and IAM-based resource filtering</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-17-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-17-discoveryengine-v1</id>
    <published>2026-09-17T00:00:00Z</published>
    <updated>2026-09-17T00:00:00Z</updated>
    <summary type="text">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 &apos;family&apos; field read-only.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>Track Play Store status in AppStoreAppActiveApkSet</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-17-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-17-androidpublisher-v3</id>
    <published>2026-09-17T00:00:00Z</published>
    <updated>2026-09-17T00:00:00Z</updated>
    <summary type="text">Developers can now explicitly flag if APK sets are already published on Google Play and provide a corresponding version code.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>CMEK support for Query Templates</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-17-analyticshub-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-17-analyticshub-v1</id>
    <published>2026-09-17T00:00:00Z</published>
    <updated>2026-09-17T00:00:00Z</updated>
    <summary type="text">Analytics Hub now supports Customer-Managed Encryption Keys (CMEK) for Query Templates, allowing developers to encrypt template definitions using their own KMS keys.</summary>
    <category term="Data Analytics" />
    <category term="Analytics Hub" />
    <category term="analyticshub.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Cloud SQL introduces Workload Capture and Replay</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-16-sqladmin-v1beta4" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-16-sqladmin-v1beta4</id>
    <published>2026-09-16T00:00:00Z</published>
    <updated>2026-09-16T00:00:00Z</updated>
    <summary type="text">Cloud SQL adds a new suite of methods to capture production database traffic and replay it on test instances for performance and upgrade validation.</summary>
    <category term="Databases" />
    <category term="Cloud SQL" />
    <category term="sqladmin.v1beta4" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Strict schema rules and new methods for Workload Capture</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-16-sqladmin-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-16-sqladmin-v1</id>
    <published>2026-09-16T00:00:00Z</published>
    <updated>2026-09-16T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Databases" />
    <category term="Cloud SQL" />
    <category term="sqladmin.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] MigrationSummary endTime is now read-only</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-16-metastore-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-16-metastore-v1beta</id>
    <published>2026-09-16T00:00:00Z</published>
    <updated>2026-09-16T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] MigrationSummary timestamps updated in Metastore v1alpha</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-16-metastore-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-16-metastore-v1alpha</id>
    <published>2026-09-16T00:00:00Z</published>
    <updated>2026-09-16T00:00:00Z</updated>
    <summary type="text">The MigrationSummary schema now marks endTime as read-only and redefines createTime to reflect the start of metadata reads.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] MigrationSummary schema updates and breaking changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-16-metastore-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-16-metastore-v1</id>
    <published>2026-09-16T00:00:00Z</published>
    <updated>2026-09-16T00:00:00Z</updated>
    <summary type="text">The MigrationSummary schema has been updated with a new read-only endTime field and revised semantics for createTime.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1" />
  </entry>
  <entry>
    <title>Dataproc deprecates diskType in favor of type for Hyperdisks</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-15-dataproc-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-15-dataproc-v1</id>
    <published>2026-09-15T00:00:00Z</published>
    <updated>2026-09-15T00:00:00Z</updated>
    <summary type="text">Dataproc&apos;s AttachedDiskConfig schema has deprecated the diskType field, introducing a new type field for specifying Hyperdisk configurations.</summary>
    <category term="Data Analytics" />
    <category term="Cloud Dataproc" />
    <category term="dataproc.v1" />
  </entry>
  <entry>
    <title>New extended data type URL for Object Custom Context</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-14-storage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-14-storage-v1</id>
    <published>2026-09-14T00:00:00Z</published>
    <updated>2026-09-14T00:00:00Z</updated>
    <summary type="text">Cloud Storage has added an extendedDataTypeUrl field to the ObjectCustomContextPayload schema to better identify custom context data.</summary>
    <category term="Storage" />
    <category term="Cloud Storage" />
    <category term="storage.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] NotebookLM API Restored with Stricter Schema Constraints</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-14-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-14-discoveryengine-v1alpha</id>
    <published>2026-09-14T00:00:00Z</published>
    <updated>2026-09-14T00:00:00Z</updated>
    <summary type="text">The NotebookLM alpha API surface has been reinstated after a recent removal, now featuring stricter parameter requirements and immutable fields.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>BigQuery adds GCS mounts for Python UDFs and native UUIDs</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-13-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-13-bigquery-v2</id>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-13T00:00:00Z</updated>
    <summary type="text">BigQuery now supports mounting GCS buckets as volumes for Python UDFs and introduces a native UUID data type for SQL schemas.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>Minor terminology update in AgentTool documentation</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-12-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-12-aiplatform-v1</id>
    <published>2026-09-12T00:00:00Z</published>
    <updated>2026-09-12T00:00:00Z</updated>
    <summary type="text">A minor documentation update for Vertex AI Agents changes references from &apos;GCP&apos; to &apos;Google Cloud&apos; in the AgentTool schema.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataform adds BigQuery Unit Tests and End-User Auth</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-10-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-10-dataform-v1beta1</id>
    <published>2026-09-10T00:00:00Z</published>
    <updated>2026-09-10T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataform adds BigQuery Unit Testing and End-User Auth</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-10-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-10-dataform-v1</id>
    <published>2026-09-10T00:00:00Z</published>
    <updated>2026-09-10T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
  <entry>
    <title>Data Protection Policies and Session Management Controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-09-discoveryengine-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-09-discoveryengine-v1beta</id>
    <published>2026-09-09T00:00:00Z</published>
    <updated>2026-09-09T00:00:00Z</updated>
    <summary type="text">Vertex AI Agent Builder adds native Sensitive Data Protection integration for data stores and connectors, alongside new session management controls and model &apos;thinking&apos; levels.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] NotebookLM Alpha Removed &amp; New Data Protection Policies</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-09-discoveryengine-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-09-discoveryengine-v1alpha</id>
    <published>2026-09-09T00:00:00Z</published>
    <updated>2026-09-09T00:00:00Z</updated>
    <summary type="text">This update includes a massive breaking change removing the NotebookLM alpha API surface while introducing new Sensitive Data Protection integrations and session management controls.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Data Protection Policies and Session Management Controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-09-discoveryengine-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-09-discoveryengine-v1</id>
    <published>2026-09-09T00:00:00Z</published>
    <updated>2026-09-09T00:00:00Z</updated>
    <summary type="text">Discovery Engine introduces Sensitive Data Protection (DLP) integration, configurable session management for Engines, and a breaking change making icon URLs read-only.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI Agent Builder" />
    <category term="discoveryengine.v1" />
  </entry>
  <entry>
    <title>Deprecation of Public/Private App Visibility Permission</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-09-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-09-androidpublisher-v3</id>
    <published>2026-09-09T00:00:00Z</published>
    <updated>2026-09-09T00:00:00Z</updated>
    <summary type="text">A specific developer account permission related to public/private app visibility has been deprecated and is no longer supported.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>Clarification on AppStoreAppActiveApkSet versioning</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-08-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-08-androidpublisher-v3</id>
    <published>2026-09-08T00:00:00Z</published>
    <updated>2026-09-08T00:00:00Z</updated>
    <summary type="text">The API documentation now explicitly states that all APKs within an AppStoreAppActiveApkSet must belong to the same app version.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Secret Manager integration for transfer parameters</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-07-bigquerydatatransfer-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-07-bigquerydatatransfer-v1</id>
    <published>2026-09-07T00:00:00Z</published>
    <updated>2026-09-07T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Data Transfer Service" />
    <category term="bigquerydatatransfer.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: Breaking Parameter Changes &amp; Auth Scope Shift</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-04-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-04-aiplatform-v1beta1</id>
    <published>2026-09-04T00:00:00Z</published>
    <updated>2026-09-04T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI shifts to granular OAuth scopes</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-04-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-04-aiplatform-v1</id>
    <published>2026-09-04T00:00:00Z</published>
    <updated>2026-09-04T00:00:00Z</updated>
    <summary type="text">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.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Time-bound Role Assignments in Directory API</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-04-admin-directory-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-04-admin-directory-v1</id>
    <published>2026-09-04T00:00:00Z</published>
    <updated>2026-09-04T00:00:00Z</updated>
    <summary type="text">The Directory API now supports expiring role assignments, allowing administrators to set a specific timestamp for when a user&apos;s role should be automatically revoked.</summary>
    <category term="Data Analytics" />
    <category term="Admin SDK" />
    <category term="admin.directory_v1" />
  </entry>
  <entry>
    <title>Drive files.copy now supports copying comments</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-03-drive-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-03-drive-v3</id>
    <published>2026-09-03T00:00:00Z</published>
    <updated>2026-09-03T00:00:00Z</updated>
    <summary type="text">The Drive API now allows developers to include comments when duplicating files via the files.copy method.</summary>
    <category term="Data Analytics" />
    <category term="Google Drive API" />
    <category term="drive.v3" />
  </entry>
  <entry>
    <title>Minor documentation update for Assignment principal</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-03-bigqueryreservation-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-03-bigqueryreservation-v1</id>
    <published>2026-09-03T00:00:00Z</published>
    <updated>2026-09-03T00:00:00Z</updated>
    <summary type="text">The description for the principal field in the Assignment resource has been updated for clarity and grammatical consistency.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Reservation" />
    <category term="bigqueryreservation.v1" />
  </entry>
  <entry>
    <title>Granular Scopes for Video Ratings</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-02-youtube-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-02-youtube-v3</id>
    <published>2026-09-02T00:00:00Z</published>
    <updated>2026-09-02T00:00:00Z</updated>
    <summary type="text">The videos.getRating method now supports the youtube.readonly scope, allowing for more restricted access to rating data.</summary>
    <category term="Data Analytics" />
    <category term="YouTube Data API" />
    <category term="youtube.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Cloud Billing adds Agent Messaging and Task Management</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-02-cloudbilling-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-02-cloudbilling-v1</id>
    <published>2026-09-02T00:00:00Z</published>
    <updated>2026-09-02T00:00:00Z</updated>
    <summary type="text">The Cloud Billing API has introduced a new interaction model involving &apos;agents&apos; and &apos;tasks&apos;, while enforcing stricter requirements on existing parameters.</summary>
    <category term="FinOps &amp; Billing" />
    <category term="Cloud Billing" />
    <category term="cloudbilling.v1" />
  </entry>
  <entry>
    <title>Support for External Link Reporting and Game Reward Limits</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-01-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-01-androidpublisher-v3</id>
    <published>2026-09-01T00:00:00Z</published>
    <updated>2026-09-01T00:00:00Z</updated>
    <summary type="text">The API now supports reporting for external content link transactions and introduces redemption limits for game-specific one-time product offers.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Scoped Search and SQL Dialect Controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-29-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-29-dataplex-v1</id>
    <published>2026-08-29T00:00:00Z</published>
    <updated>2026-08-29T00:00:00Z</updated>
    <summary type="text">Dataplex introduces scoped searching via a new contexts parameter and adds support for specifying SQL dialects in data documentation, alongside a breaking schema change.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking Changes to Agents and Transcription Config</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-29-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-29-aiplatform-v1beta1</id>
    <published>2026-08-29T00:00:00Z</published>
    <updated>2026-08-29T00:00:00Z</updated>
    <summary type="text">Vertex AI v1beta1 introduces several breaking changes, including mandatory resource parameters and the removal of the recently added transcription &apos;mode&apos;. It also adds standard IAM policy management for Agents and new sandbox authorization methods.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI Agents get IAM controls and lifecycle updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-29-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-29-aiplatform-v1</id>
    <published>2026-08-29T00:00:00Z</published>
    <updated>2026-08-29T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces IAM support and enhanced deletion controls for Agents, alongside significant breaking changes to Sandbox networking and Audio Transcription configurations.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Deprecation of Container Combine and Move Tag Methods</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-27-tagmanager-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-27-tagmanager-v2</id>
    <published>2026-08-27T00:00:00Z</published>
    <updated>2026-08-27T00:00:00Z</updated>
    <summary type="text">Google Tag Manager has deprecated the `combine` and `move_tag_id` methods within the containers resource, signaling a shift in how container migrations are handled.</summary>
    <category term="Data Analytics" />
    <category term="Tag Manager" />
    <category term="tagmanager.v2" />
  </entry>
  <entry>
    <title>Clarified field requirements for Drive Approvals</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-27-drive-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-27-drive-v3</id>
    <published>2026-08-27T00:00:00Z</published>
    <updated>2026-08-27T00:00:00Z</updated>
    <summary type="text">The Drive API documentation now explicitly notes that the approvals.list method requires the fields parameter to return detailed results.</summary>
    <category term="Data Analytics" />
    <category term="Google Drive API" />
    <category term="drive.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] YouTube Data API v3: Major Breaking Changes &amp; Strict Validation</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-youtube-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-youtube-v3</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">A significant update to the YouTube Data API v3 enforces strict requirements for core parameters and marks several video statistic fields as read-only. Developers must update their requests to include mandatory fields like part, id, and channelId.</summary>
    <category term="Data Analytics" />
    <category term="YouTube Data API" />
    <category term="youtube.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Apps Script API enforces required IDs and expands scopes</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-script-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-script-v1</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">The Apps Script API now strictly requires scriptId, deploymentId, and versionNumber in relevant methods, while significantly expanding its list of supported OAuth2 scopes.</summary>
    <category term="Data Analytics" />
    <category term="Apps Script" />
    <category term="script.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking: Library Agent enforces required parameters</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-libraryagent-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-libraryagent-v1</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">The Library Agent API has updated its schema to enforce &apos;name&apos; and &apos;parent&apos; as strictly required parameters while adding standard GCP global parameters.</summary>
    <category term="Data Analytics" />
    <category term="Library Agent" />
    <category term="libraryagent.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Gmail API: Strict Parameter Validation &amp; CSE Immutability</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-gmail-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-gmail-v1</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">The Gmail API has updated its discovery document to enforce strict requirement checks on core parameters and transition several Client-Side Encryption (CSE) fields to read-only status.</summary>
    <category term="Data Analytics" />
    <category term="Gmail API" />
    <category term="gmail.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Drive API v3: Major Schema Hardening and Breaking Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-drive-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-drive-v3</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">Google Drive API v3 has introduced significant breaking changes by making numerous ID parameters strictly required and marking several schema properties as read-only.</summary>
    <category term="Data Analytics" />
    <category term="Google Drive API" />
    <category term="drive.v3" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Drive v2 API: Major Validation Tightening &amp; Breaking Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-drive-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-drive-v2</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">The Drive v2 API discovery document has been updated to enforce strict requirements on resource identifiers and mark several metadata fields as read-only.</summary>
    <category term="Data Analytics" />
    <category term="Google Drive API" />
    <category term="drive.v2" />
  </entry>
  <entry>
    <title>Massive Schema Tightening and New Data Safety Method</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-androidpublisher-v3" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-androidpublisher-v3</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">Dozens of parameters are now strictly required and many schema fields have become read-only, alongside a new method for Safety Labels.</summary>
    <category term="Data Analytics" />
    <category term="Android Publisher" />
    <category term="androidpublisher.v3" />
  </entry>
  <entry>
    <title>Breaking Changes and Workspace Studio Support</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-admin-reports-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-admin-reports-v1</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">The Reports API has introduced breaking changes regarding required parameters and read-only fields, while also expanding support for Workspace Studio applications in audit logs.</summary>
    <category term="Data Analytics" />
    <category term="Admin SDK" />
    <category term="admin.reports_v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Major Schema Hardening and Granular OAuth Scopes</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-admin-directory-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-admin-directory-v1</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">The Directory API has undergone a significant hardening phase, making dozens of parameters strictly required and marking system-generated fields as read-only. It also introduces a wide array of granular OAuth2 scopes for more precise access control.</summary>
    <category term="Data Analytics" />
    <category term="Admin SDK" />
    <category term="admin.directory_v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking changes and parameter enforcement in Data Transfer</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-25-admin-datatransfer-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-25-admin-datatransfer-v1</id>
    <published>2026-08-25T00:00:00Z</published>
    <updated>2026-08-25T00:00:00Z</updated>
    <summary type="text">The Data Transfer API now strictly enforces required ID parameters and has updated its discovery surface to include standard Google API parameters and mTLS support.</summary>
    <category term="Data Analytics" />
    <category term="Admin SDK" />
    <category term="admin.datatransfer_v1" />
  </entry>
  <entry>
    <title>CEL Conditions and Precedence for Reservation Assignments</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-22-bigqueryreservation-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-22-bigqueryreservation-v1</id>
    <published>2026-08-22T00:00:00Z</published>
    <updated>2026-08-22T00:00:00Z</updated>
    <summary type="text">BigQuery is introducing logic-based reservation assignments using Common Expression Language (CEL) and a new precedence system to resolve matching conflicts.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Reservation" />
    <category term="bigqueryreservation.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Smart Transcription, Multi-Speaker Config, and Agentic Video</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-22-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-22-aiplatform-v1beta1</id>
    <published>2026-08-22T00:00:00Z</published>
    <updated>2026-08-22T00:00:00Z</updated>
    <summary type="text">Vertex AI adds a &apos;Smart&apos; transcription mode for automated cleanup of audio transcripts and introduces multi-speaker configurations. Video generation is enhanced with a new &apos;Extend&apos; task and agentic processing modes for dynamic frame navigation.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI adds Response Management and Smart Transcription</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-22-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-22-aiplatform-v1</id>
    <published>2026-08-22T00:00:00Z</published>
    <updated>2026-08-22T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces lifecycle management for endpoint responses and a new &quot;Smart&quot; mode for audio transcription that automatically cleans up disfluencies.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Git branch management arrives for Dataform Workspaces</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-21-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-21-dataform-v1beta1</id>
    <published>2026-08-21T00:00:00Z</published>
    <updated>2026-08-21T00:00:00Z</updated>
    <summary type="text">Dataform Workspaces now support native Git branch operations including checkout, fetch, and delete, enabling better programmatic control over development environments.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>Data Catalog adds support for Graph Nodes and Edges</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-19-datacatalog-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-19-datacatalog-v1beta1</id>
    <published>2026-08-19T00:00:00Z</published>
    <updated>2026-08-19T00:00:00Z</updated>
    <summary type="text">Data Catalog now supports NODE and EDGE entry types, enabling metadata management for graph-based data structures.</summary>
    <category term="Data Analytics" />
    <category term="Data Catalog" />
    <category term="datacatalog.v1beta1" />
  </entry>
  <entry>
    <title>Data Catalog adds NODE and EDGE entry types</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-19-datacatalog-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-19-datacatalog-v1</id>
    <published>2026-08-19T00:00:00Z</published>
    <updated>2026-08-19T00:00:00Z</updated>
    <summary type="text">Data Catalog now supports graph-based metadata with new NODE and EDGE entry types, allowing for more granular classification of graph-related assets.</summary>
    <category term="Data Analytics" />
    <category term="Data Catalog" />
    <category term="datacatalog.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Video Outpainting, Audio Control, and Monitoring Refinements</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-14-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-14-aiplatform-v1beta1</id>
    <published>2026-08-14T00:00:00Z</published>
    <updated>2026-08-14T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces advanced video generation capabilities including outpainting and audio control, while refining agent monitoring filters and deprecating legacy ASR fields.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI adds Video Outpainting and Advanced Audio Control</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-14-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-14-aiplatform-v1</id>
    <published>2026-08-14T00:00:00Z</published>
    <updated>2026-08-14T00:00:00Z</updated>
    <summary type="text">Vertex AI expands its video generation experimental suite with new capabilities for outpainting, video-to-video transformations, and granular audio track management.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Looker adds ESA migration support to ExportMetadata</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-13-looker-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-13-looker-v1</id>
    <published>2026-08-13T00:00:00Z</published>
    <updated>2026-08-13T00:00:00Z</updated>
    <summary type="text">Looker&apos;s ExportMetadata schema now includes a field for specifying source BigQuery datasets during Elite System Activity (ESA) migrations.</summary>
    <category term="Data Analytics" />
    <category term="Looker Core" />
    <category term="looker.v1" />
  </entry>
  <entry>
    <title>New jobType for Materialized View Refresh assignments</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-09-bigqueryreservation-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-09-bigqueryreservation-v1</id>
    <published>2026-08-09T00:00:00Z</published>
    <updated>2026-08-09T00:00:00Z</updated>
    <summary type="text">BigQuery now supports assigning reservations specifically for automated materialized view refreshes, allowing for better resource isolation and prioritization.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Reservation" />
    <category term="bigqueryreservation.v1" />
  </entry>
  <entry>
    <title>Dataplex adds ChangeRequest comments and EntryLinkType events</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-07-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-07-dataplex-v1</id>
    <published>2026-08-07T00:00:00Z</published>
    <updated>2026-08-07T00:00:00Z</updated>
    <summary type="text">Dataplex now supports reviewer comments on ChangeRequests and introduces a new event schema for tracking EntryLinkType lifecycle changes.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: Session Compaction and Transcription Refactor</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-07-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-07-aiplatform-v1beta1</id>
    <published>2026-08-07T00:00:00Z</published>
    <updated>2026-08-07T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces session compaction for long-running agent histories and standardizes speech transcription configurations, alongside a breaking change to traffic type enums.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI adds Session Compaction and Audio API updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-07-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-07-aiplatform-v1</id>
    <published>2026-08-07T00:00:00Z</published>
    <updated>2026-08-07T00:00:00Z</updated>
    <summary type="text">Reasoning Engines now support session history compaction to manage context windows via summarization. Audio transcription APIs are being streamlined with new language code fields, and evaluation runs gain CMEK support.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Support for Notebooks, SQL assets, and GCS snapshots</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-06-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-06-dataform-v1beta1</id>
    <published>2026-08-06T00:00:00Z</published>
    <updated>2026-08-06T00:00:00Z</updated>
    <summary type="text">Dataform is expanding beyond standard projects to support single-file SQL and Notebook assets, alongside GCS-based repository snapshots for scheduled executions.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>Dataform adds support for SQL and Notebook pipelines</title>
    <link href="https://google-cloud-radar.com/changes/2026-08-06-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-08-06-dataform-v1</id>
    <published>2026-08-06T00:00:00Z</published>
    <updated>2026-08-06T00:00:00Z</updated>
    <summary type="text">Dataform is expanding beyond standard projects to support SQL and Notebook assets as first-class pipelines. New features also include GCS repository snapshotting for scheduled notebook execution.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
  <entry>
    <title>Deprecation of proposer field in QueryTemplate</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-30-analyticshub-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-30-analyticshub-v1</id>
    <published>2026-07-30T00:00:00Z</published>
    <updated>2026-07-30T00:00:00Z</updated>
    <summary type="text">The proposer field in the QueryTemplate schema is now formally deprecated in favor of primary_contact.</summary>
    <category term="Data Analytics" />
    <category term="Analytics Hub" />
    <category term="analyticshub.v1" />
  </entry>
  <entry>
    <title>Vertex AI: Task Stores, Speech Transcription, and Model Proxies</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-30-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-30-aiplatform-v1beta1</id>
    <published>2026-07-30T00:00:00Z</published>
    <updated>2026-07-30T00:00:00Z</updated>
    <summary type="text">Vertex AI expands agentic capabilities with Task Stores for decoupled task management and integrated speech-to-text transcription for generative models.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI adds Compact HTTP Forwarding and Serving Operations</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-30-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-30-aiplatform-v1</id>
    <published>2026-07-30T00:00:00Z</published>
    <updated>2026-07-30T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces a &apos;compact&apos; HTTP forwarding method for publisher endpoints and adds standard long-running operation management for Serving Profiles.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>TLS Configuration for BigQuery Connections</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-26-bigqueryconnection-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-26-bigqueryconnection-v1</id>
    <published>2026-07-26T00:00:00Z</published>
    <updated>2026-07-26T00:00:00Z</updated>
    <summary type="text">BigQuery connections now support granular TLS configuration, including support for Private PKI and custom CA certificates.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Connection API" />
    <category term="bigqueryconnection.v1" />
  </entry>
  <entry>
    <title>Explicit statement types and new data skew metrics</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-26-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-26-bigquery-v2</id>
    <published>2026-07-26T00:00:00Z</published>
    <updated>2026-07-26T00:00:00Z</updated>
    <summary type="text">BigQuery now explicitly identifies the SQL statement type in query responses and provides new percentile-based metrics for detecting data skew in query stages.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: Memory Bank Expansion &amp; Breaking Agent Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-26-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-26-aiplatform-v1beta1</id>
    <published>2026-07-26T00:00:00Z</published>
    <updated>2026-07-26T00:00:00Z</updated>
    <summary type="text">New event ingestion and profile retrieval methods for Memory Banks expand agentic capabilities, while breaking changes remove several fields from Agent and Tool result schemas.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI adds Audio Transcription and Memory Event Ingestion</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-26-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-26-aiplatform-v1</id>
    <published>2026-07-26T00:00:00Z</published>
    <updated>2026-07-26T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces native audio transcription schemas and expands agent memory capabilities with event ingestion. New controls for video generation rewriters and granular index endpoint updates are also now available.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>New reservationGroupPath field for hierarchical tracking</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-24-bigqueryreservation-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-24-bigqueryreservation-v1</id>
    <published>2026-07-24T00:00:00Z</published>
    <updated>2026-07-24T00:00:00Z</updated>
    <summary type="text">The Reservation resource now includes a read-only reservationGroupPath array, providing the full lineage of a reservation within hierarchical groups.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Reservation" />
    <category term="bigqueryreservation.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: Breaking GenAI Schema Changes &amp; New Retrieval Tools</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-18-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-18-aiplatform-v1beta1</id>
    <published>2026-07-18T00:00:00Z</published>
    <updated>2026-07-18T00:00:00Z</updated>
    <summary type="text">This update introduces significant breaking changes by removing generation penalties and caching fields, while adding new proxy methods for model responses and expanding retrieval tool support for agents.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI adds HTTP request forwarding and video alignment</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-18-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-18-aiplatform-v1</id>
    <published>2026-07-18T00:00:00Z</published>
    <updated>2026-07-18T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces a flexible HTTP forwarding method for publisher endpoints and adds experimental alignment controls for video generation and grounding observability.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Breaking: context field removed from LookupContextRequest</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-15-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-15-dataplex-v1</id>
    <published>2026-07-15T00:00:00Z</published>
    <updated>2026-07-15T00:00:00Z</updated>
    <summary type="text">The optional context string has been removed from the LookupContextRequest schema, affecting metadata lookup workflows.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>Vertex AI adds Memory Bank CRUD and Streaming Event updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-14-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-14-aiplatform-v1beta1</id>
    <published>2026-07-14T00:00:00Z</published>
    <updated>2026-07-14T00:00:00Z</updated>
    <summary type="text">Vertex AI expands its Reasoning Engine capabilities with full CRUD support for Memory Banks and introduces a distinction between legacy and step-based streaming events.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI adds CRUD and Generation for Agent Memories</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-14-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-14-aiplatform-v1</id>
    <published>2026-07-14T00:00:00Z</published>
    <updated>2026-07-14T00:00:00Z</updated>
    <summary type="text">Vertex AI expands its memory management capabilities, allowing developers to create, list, and automatically generate persistent memories for AI agents within the Reasoning Engine framework.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Table-valued arguments and multi-cloud storage stats</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-09-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-09-bigquery-v2</id>
    <published>2026-07-09T00:00:00Z</published>
    <updated>2026-07-09T00:00:00Z</updated>
    <summary type="text">BigQuery now supports table-valued arguments for routines and provides granular object storage statistics for multi-cloud queries. Developers can also now force on-demand billing by setting reservations to &apos;none&apos;.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Removal of metadataDestination from TransferRun</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-06-bigquerydatatransfer-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-06-bigquerydatatransfer-v1</id>
    <published>2026-07-06T00:00:00Z</published>
    <updated>2026-07-06T00:00:00Z</updated>
    <summary type="text">The output-only metadataDestination field has been removed from the TransferRun resource schema.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Data Transfer Service" />
    <category term="bigquerydatatransfer.v1" />
  </entry>
  <entry>
    <title>Vertex AI adds Claude-specific feature controls</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-06-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-06-aiplatform-v1beta1</id>
    <published>2026-07-06T00:00:00Z</published>
    <updated>2026-07-06T00:00:00Z</updated>
    <summary type="text">Developers using Anthropic&apos;s Claude models on Vertex AI now have a dedicated configuration for advanced AI features and data retention opt-ins.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI: New Memory Bank Resources and Agent Refinements</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-03-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-03-aiplatform-v1beta1</id>
    <published>2026-07-03T00:00:00Z</published>
    <updated>2026-07-03T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces MemoryBanks and Memories for persistent agent state management, alongside schema refinements for Monitored Agents and user scenario generation.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI adds Memory management and Agent configuration updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-03-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-03-aiplatform-v1</id>
    <published>2026-07-03T00:00:00Z</published>
    <updated>2026-07-03T00:00:00Z</updated>
    <summary type="text">Vertex AI introduces long-running operation management for Memory resources and updates Agent scenario generation to support Gemini-based configurations.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Dataplex Data Domains add IAM policy member metadata</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-02-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-02-dataplex-v1</id>
    <published>2026-07-02T00:00:00Z</published>
    <updated>2026-07-02T00:00:00Z</updated>
    <summary type="text">The recently introduced DataDomain resource now includes output-only IAM policy member strings, supporting both name-based and UID-based identity principals.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] New Automatic Number Conversion and Error Schema Cleanup</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-01-tagmanager-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-01-tagmanager-v2</id>
    <published>2026-07-01T00:00:00Z</published>
    <updated>2026-07-01T00:00:00Z</updated>
    <summary type="text">Added automatic decimal separator detection for variable formatting and significantly reduced the surface area of the CompilerErrorLite schema.</summary>
    <category term="Data Analytics" />
    <category term="Tag Manager" />
    <category term="tagmanager.v2" />
  </entry>
  <entry>
    <title>Hierarchical Reservation Groups and Flex Plan Deprecation</title>
    <link href="https://google-cloud-radar.com/changes/2026-07-01-bigqueryreservation-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-07-01-bigqueryreservation-v1</id>
    <published>2026-07-01T00:00:00Z</published>
    <updated>2026-07-01T00:00:00Z</updated>
    <summary type="text">BigQuery Reservation API adds support for updating reservation groups and hierarchical structures while deprecating Flex capacity commitments.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Reservation" />
    <category term="bigqueryreservation.v1" />
  </entry>
  <entry>
    <title>New score display modes for Lighthouse categories</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-30-pagespeedonline-v5" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-30-pagespeedonline-v5</id>
    <published>2026-06-30T00:00:00Z</published>
    <updated>2026-06-30T00:00:00Z</updated>
    <summary type="text">The PageSpeed Insights API now includes metadata on how category scores should be visually represented, adding support for fractional scoring.</summary>
    <category term="Data Analytics" />
    <category term="PageSpeed Insights" />
    <category term="pagespeedonline.v5" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI Beta: Computer Use Safety &amp; Breaking Agent Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-27-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-27-aiplatform-v1beta1</id>
    <published>2026-06-27T00:00:00Z</published>
    <updated>2026-06-27T00:00:00Z</updated>
    <summary type="text">Vertex AI adds prompt injection detection for computer-use tasks and Zero Data Retention for Parallel AI Search, alongside significant removals of Agent-related methods.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Vertex AI introduces Agents and Semantic Governance resources</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-27-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-27-aiplatform-v1</id>
    <published>2026-06-27T00:00:00Z</published>
    <updated>2026-06-27T00:00:00Z</updated>
    <summary type="text">Vertex AI has significantly expanded its v1 API surface, introducing dedicated resources for managing AI Agents and a new Semantic Governance Policy Engine.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Native Apache Arrow support for query results</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-26-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-26-bigquery-v2</id>
    <published>2026-06-26T00:00:00Z</published>
    <updated>2026-06-26T00:00:00Z</updated>
    <summary type="text">BigQuery is introducing native Apache Arrow support for query results, enabling high-performance columnar data transfer directly from the query API.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>Dataplex introduces Data Domains for logical organization</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-25-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-25-dataplex-v1</id>
    <published>2026-06-25T00:00:00Z</published>
    <updated>2026-06-25T00:00:00Z</updated>
    <summary type="text">Dataplex adds a new DataDomain resource type, enabling developers to create, list, and manage logical data boundaries within a project and location.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>Documentation cleanup and internal lint removal</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-24-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-24-dataform-v1beta1</id>
    <published>2026-06-24T00:00:00Z</published>
    <updated>2026-06-24T00:00:00Z</updated>
    <summary type="text">Minor updates to parameter and field descriptions, primarily removing internal linting instructions and improving formatting.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>Minor documentation cleanup and formatting</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-24-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-24-dataform-v1</id>
    <published>2026-06-24T00:00:00Z</published>
    <updated>2026-06-24T00:00:00Z</updated>
    <summary type="text">This update consists of minor documentation refinements, including the removal of internal linting comments and improved formatting for resource names in descriptions.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
  <entry>
    <title>New Agentic Browsing category added to PageSpeed API</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-23-pagespeedonline-v5" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-23-pagespeedonline-v5</id>
    <published>2026-06-23T00:00:00Z</published>
    <updated>2026-06-23T00:00:00Z</updated>
    <summary type="text">The PageSpeed Insights API now supports a new audit category called AGENTIC_BROWSING to evaluate site compatibility with AI agents.</summary>
    <category term="Data Analytics" />
    <category term="PageSpeed Insights" />
    <category term="pagespeedonline.v5" />
  </entry>
  <entry>
    <title>New ingestion rule integrations for BigQuery and Airflow</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-23-datalineage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-23-datalineage-v1</id>
    <published>2026-06-23T00:00:00Z</published>
    <updated>2026-06-23T00:00:00Z</updated>
    <summary type="text">The Data Lineage API now supports BigQuery and Managed Service for Apache Airflow (Cloud Composer) in ingestion rule configurations.</summary>
    <category term="Data Analytics" />
    <category term="Data Lineage" />
    <category term="datalineage.v1" />
  </entry>
  <entry>
    <title>Python UDF concurrency documentation update</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-23-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-23-bigquery-v2</id>
    <published>2026-06-23T00:00:00Z</published>
    <updated>2026-06-23T00:00:00Z</updated>
    <summary type="text">Updated documentation for Python UDF concurrency settings in ExternalRuntimeOptions, adding links to configuration guides.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>Clarified transferredBytes for BigQuery Omni</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-22-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-22-bigquery-v2</id>
    <published>2026-06-22T00:00:00Z</published>
    <updated>2026-06-22T00:00:00Z</updated>
    <summary type="text">The description for transferredBytes in query statistics has been updated to specifically define its role in BigQuery Omni data movement.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>BigLake API rebranded to Lakehouse API</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-22-biglake-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-22-biglake-v1</id>
    <published>2026-06-22T00:00:00Z</published>
    <updated>2026-06-22T00:00:00Z</updated>
    <summary type="text">The BigLake API has been officially rebranded to the Lakehouse API in documentation, signaling a shift toward a unified metastore for multi-engine data lakes.</summary>
    <category term="Data Analytics" />
    <category term="BigLake" />
    <category term="biglake.v1" />
  </entry>
  <entry>
    <title>Deprecation of Destination methods in Tag Manager</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-tagmanager-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-tagmanager-v2</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">Google Tag Manager has officially marked the &apos;get&apos; and &apos;link&apos; methods for the destinations resource as deprecated.</summary>
    <category term="Data Analytics" />
    <category term="Tag Manager" />
    <category term="tagmanager.v2" />
  </entry>
  <entry>
    <title>New Agentic Browsing Lighthouse Category</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-pagespeedonline-v5" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-pagespeedonline-v5</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">PageSpeed Insights has introduced a new &apos;agentic-browsing&apos; category to its Lighthouse audit results.</summary>
    <category term="Data Analytics" />
    <category term="PageSpeed Insights" />
    <category term="pagespeedonline.v5" />
  </entry>
  <entry>
    <title>Looker v1 adds Instance Undelete and Release Channels</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-looker-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-looker-v1</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">Looker Core instances now support soft-deletion recovery and configurable update release channels (Rapid, Regular, Stable).</summary>
    <category term="Data Analytics" />
    <category term="Looker Core" />
    <category term="looker.v1" />
  </entry>
  <entry>
    <title>Dataplex adds Unstructured Data Profiling and Graph Profiles</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-dataplex-v1</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">Dataplex expands its scanning capabilities with support for unstructured data profiling and a new graph-based profiling schema for semantic inference.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>Dataform introduces event-driven triggers and Git links</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-dataform-v1beta1</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">Dataform workflows can now be triggered automatically by table updates, and Git remote settings now support direct repository links for machine credentials.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>Dataform adds GitRepositoryLink for machine credentials</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-dataform-v1</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">Dataform now supports linking Git repository resources for machine credentials, simplifying authentication for automated workflows.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
  <entry>
    <title>Generic HTTP request execution added to Connectors</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-connectors-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-connectors-v2</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">Integration Connectors now supports a raw executeHttpRequest method, allowing developers to send arbitrary HTTP requests through existing connections.</summary>
    <category term="Integration Services" />
    <category term="Integration Connectors" />
    <category term="connectors.v2" />
  </entry>
  <entry>
    <title>Dataplex Universal Catalog integration for Data Transfers</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-bigquerydatatransfer-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-bigquerydatatransfer-v1</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">BigQuery Data Transfer Service now supports automated metadata import into Dataplex Universal Catalog during data transfers.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Data Transfer Service" />
    <category term="bigquerydatatransfer.v1" />
  </entry>
  <entry>
    <title>BigQuery API clarifies IAM requirements across all methods</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-bigquery-v2</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">The BigQuery v2 discovery document has been updated to explicitly document the IAM permissions required for nearly every API method, simplifying least-privilege configuration.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>Analytics Hub adds ZLIB compression for message transforms</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-analyticshub-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-analyticshub-v1</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">Analytics Hub now supports ZLIB compression and decompression within message transformations, alongside updated row key logic for Bigtable subscriptions.</summary>
    <category term="Data Analytics" />
    <category term="Analytics Hub" />
    <category term="analyticshub.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Vertex AI Beta: New Governance Engines and Breaking Agent Changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-aiplatform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-aiplatform-v1beta1</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">This update introduces Semantic Governance Policy Engines and Agent Anomaly Detection while introducing several breaking changes to the Agents and Interactions APIs.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1beta1" />
  </entry>
  <entry>
    <title>Online Evaluator Operations and GenerationConfig Deprecations</title>
    <link href="https://google-cloud-radar.com/changes/2026-06-21-aiplatform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-06-21-aiplatform-v1</id>
    <published>2026-06-21T00:00:00Z</published>
    <updated>2026-06-21T00:00:00Z</updated>
    <summary type="text">Vertex AI adds full operation management for Online Evaluators and marks several core GenerationConfig fields as deprecated in favor of a unified response format.</summary>
    <category term="Generative AI" />
    <category term="Vertex AI" />
    <category term="aiplatform.v1" />
  </entry>
  <entry>
    <title>Clarified location requirements for lineage search</title>
    <link href="https://google-cloud-radar.com/changes/2026-05-28-datalineage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-05-28-datalineage-v1</id>
    <published>2026-05-28T00:00:00Z</published>
    <updated>2026-05-28T00:00:00Z</updated>
    <summary type="text">The Data Lineage API now explicitly requires that the locations list in streaming search requests includes the location specified in the parent field.</summary>
    <category term="Data Analytics" />
    <category term="Data Lineage" />
    <category term="datalineage.v1" />
  </entry>
  <entry>
    <title>Flexible Connector Parameters and Authentication</title>
    <link href="https://google-cloud-radar.com/changes/2026-05-28-bigqueryconnection-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-05-28-bigqueryconnection-v1</id>
    <published>2026-05-28T00:00:00Z</published>
    <updated>2026-05-28T00:00:00Z</updated>
    <summary type="text">BigQuery connections now support arbitrary, connector-specific configuration and authentication parameters via a new map-based schema.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery Connection API" />
    <category term="bigqueryconnection.v1" />
  </entry>
  <entry>
    <title>Iceberg timestamp autodetection and UDF clarifications</title>
    <link href="https://google-cloud-radar.com/changes/2026-05-28-bigquery-v2" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-05-28-bigquery-v2</id>
    <published>2026-05-28T00:00:00Z</published>
    <updated>2026-05-28T00:00:00Z</updated>
    <summary type="text">BigQuery has expanded timestamp precision autodetection to Iceberg External Tables and clarified concurrency settings for Python UDFs.</summary>
    <category term="Data Analytics" />
    <category term="BigQuery" />
    <category term="bigquery.v2" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Dataplex adds Change Requests for governed resource updates</title>
    <link href="https://google-cloud-radar.com/changes/2026-05-22-dataplex-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-05-22-dataplex-v1</id>
    <published>2026-05-22T00:00:00Z</published>
    <updated>2026-05-22T00:00:00Z</updated>
    <summary type="text">Dataplex introduces a formal Change Request workflow, allowing developers to propose, list, and approve changes to data resources.</summary>
    <category term="Data Analytics" />
    <category term="Dataplex" />
    <category term="dataplex.v1" />
  </entry>
  <entry>
    <title>Granular OAuth Scopes for Data Lineage Streaming</title>
    <link href="https://google-cloud-radar.com/changes/2026-05-21-datalineage-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-05-21-datalineage-v1</id>
    <published>2026-05-21T00:00:00Z</published>
    <updated>2026-05-21T00:00:00Z</updated>
    <summary type="text">The Data Lineage API now supports specific read-only and read-write OAuth scopes for the searchLineageStreaming method, enabling better security posture.</summary>
    <category term="Data Analytics" />
    <category term="Data Lineage" />
    <category term="datalineage.v1" />
  </entry>
  <entry>
    <title>Asynchronous repository deletion and Git branch improvements</title>
    <link href="https://google-cloud-radar.com/changes/2026-05-20-dataform-v1beta1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-05-20-dataform-v1beta1</id>
    <published>2026-05-20T00:00:00Z</published>
    <updated>2026-05-20T00:00:00Z</updated>
    <summary type="text">Dataform introduces long-running repository deletion and clarifies Git default branch behavior.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1beta1" />
  </entry>
  <entry>
    <title>Improved Git branch handling and path clarifications</title>
    <link href="https://google-cloud-radar.com/changes/2026-05-20-dataform-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-05-20-dataform-v1</id>
    <published>2026-05-20T00:00:00Z</published>
    <updated>2026-05-20T00:00:00Z</updated>
    <summary type="text">Dataform now makes the Git default branch setting optional and provides a resolved &apos;effective&apos; branch field, alongside clearer path definitions for directory entries.</summary>
    <category term="Data Analytics" />
    <category term="Dataform" />
    <category term="dataform.v1" />
  </entry>
</feed>