New Revision ID for File Approvals
The `Approval` schema in the Google Drive API now includes an `approvedRevisionId` property, providing the file's revision ID upon successful approval.
Discovery API monitoring and real-time diff analysis for Google Drive API.
Never miss an API update, method deprecation, or breaking change in Google Drive API.
The `Approval` schema in the Google Drive API now includes an `approvedRevisionId` property, providing the file's revision ID upon successful approval.
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.
The Google Drive API's documentation for `permissions.create`, `delete`, and `update` methods has been updated. The warning about concurrent permission modifications is now more explicit, clarifying its scope.
The Google Drive API's permission methods (`delete`, `insert`, `patch`, `update`) now feature updated descriptions that clarify the scope of concurrent modification warnings.
The Drive API now allows developers to include comments when duplicating files via the files.copy method.
The Drive API documentation now explicitly notes that the approvals.list method requires the fields parameter to return detailed results.
Google Drive API v3 has introduced significant breaking changes by making numerous ID parameters strictly required and marking several schema properties as read-only.
The Drive v2 API discovery document has been updated to enforce strict requirements on resource identifiers and mark several metadata fields as read-only.