Data Lineage API Changes — Google Cloud RadarReal-time pre-release intelligence and changelog for Google Data Lineage. Tracked from Google Discovery Service.https://google-cloud-radar.com/services/data-lineage/atom.xml2026-10-22T00:00:00ZGoogle Cloud Radarhttps://github.com/max-ostapenko/google-cloud-radarData Lineage `runs.list` Method Gains New Scopeshttps://google-cloud-radar.com/changes/2026-10-22-datalineage-v12026-10-22T00:00:00Z2026-10-22T00:00:00ZThe `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.Filter Lineage Search by Projecthttps://google-cloud-radar.com/changes/2026-10-14-datalineage-v12026-10-14T00:00:00Z2026-10-14T00:00:00ZThe Data Lineage API now allows developers to filter `searchLineageStreaming` results by specific projects, enabling more targeted and efficient lineage queries.New ingestion rule integrations for BigQuery and Airflowhttps://google-cloud-radar.com/changes/2026-06-23-datalineage-v12026-06-23T00:00:00Z2026-06-23T00:00:00ZThe Data Lineage API now supports BigQuery and Managed Service for Apache Airflow (Cloud Composer) in ingestion rule configurations.Clarified location requirements for lineage searchhttps://google-cloud-radar.com/changes/2026-05-28-datalineage-v12026-05-28T00:00:00Z2026-05-28T00:00:00ZThe Data Lineage API now explicitly requires that the locations list in streaming search requests includes the location specified in the parent field.Granular OAuth Scopes for Data Lineage Streaminghttps://google-cloud-radar.com/changes/2026-05-21-datalineage-v12026-05-21T00:00:00Z2026-05-21T00:00:00ZThe Data Lineage API now supports specific read-only and read-write OAuth scopes for the searchLineageStreaming method, enabling better security posture.