Breaking changes lack details (@googleapis/drive)

[kenn]

Documentation Request

I'm seeing a lot of updates from 8.16.0 to 11.0.0 for @googleapis/drive in just one month, but the CHANGELOG does not describe what's breaking. Appreciate if you could add quick one-liner who should really care.

https://github.com/googleapis/google-api-nodejs-client/blob/main/src/apis/drive/CHANGELOG.md

[feywind]

Hi @kenn, at a glance it looks like the breaking changes are from proto interface changes. I guess the code tools aren't very good at distilling that stuff automatically. But here is an example. A class name change might break user code.

I agree that...

⚠ BREAKING CHANGES
drive: This release has breaking changes.
Features
drive: update the API ([b5ef473](https://github.com/googleapis/google-api-nodejs-client/commit/b5ef47311b7ec66e02429f1097345a2899cb4013))
drive: update the API ([8a7abf1](https://github.com/googleapis/google-api-nodejs-client/commit/8a7abf1b398a2c1745a16332d1738cdad359bac1))
drive: update the API ([1827fa2](https://github.com/googleapis/google-api-nodejs-client/commit/1827fa203d963dbb2524888264f2e735b3c351b7))

...is really unsatisfying. @sofisl I don't guess we have a switch to flip to make these messages more useful?

[kenn]

You may be able to feed this to Gemini 2.5 Pro to extract breaking changes? Changes look too large though.

788a311...5dd7691

[sofisl]

Hi @kenn, this library is mostly autogenerated so I don't have much more information than the actual commits.

From what I can tell, it seems that what is immediately breaking is that resources.operation was renamed to resources.operations: