<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Google Drive API API Changes — Google Cloud Radar</title>
  <subtitle>Real-time pre-release intelligence and changelog for Google Google Drive API. Tracked from Google Discovery Service.</subtitle>
  <link href="https://google-cloud-radar.com/services/google-drive-api/atom.xml" rel="self" type="application/atom+xml" />
  <link href="https://google-cloud-radar.com/services/google-drive-api" rel="alternate" type="text/html" />
  <id>https://google-cloud-radar.com/services/google-drive-api/atom.xml</id>
  <updated>2026-11-08T00:00:00Z</updated>
  <author>
    <name>Google Cloud Radar</name>
    <uri>https://github.com/max-ostapenko/google-cloud-radar</uri>
  </author>
  
  <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>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>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>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>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] 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>
</feed>