Summary
It appears that updates for @google-cloud/storage have stalled since version 7.19.0, and newer changes have not been pulled into this repository. As a result, the package is currently incompatible with google-auth-library 10.x.
Impact
Because @google-cloud/storage@7.19.0 relies on an older major version of the auth library, developers are unable to upgrade to google-auth-library@10.x. This causes dependency resolution conflicts (e.g., in npm, yarn, or pnpm) and prevents us from utilizing the latest features, bug fixes, and potential security patches provided in the v10 auth library.
Suggested Fix
Could you please look into updating the @google-cloud/storage dependencies to support google-auth-library@^10.0.0 and cut a new release?
Context
We are currently developing a GenAI project where we use Google Cloud Storage to store files and send requests. However, due to the google-auth-library version incompatibility, we are encountering a header compatibility error when making these requests. This effectively blocks our development workflow, as we cannot communicate properly with the storage service.
Summary
It appears that updates for
@google-cloud/storagehave stalled since version7.19.0, and newer changes have not been pulled into this repository. As a result, the package is currently incompatible withgoogle-auth-library10.x.Impact
Because
@google-cloud/storage@7.19.0relies on an older major version of the auth library, developers are unable to upgrade togoogle-auth-library@10.x. This causes dependency resolution conflicts (e.g., innpm,yarn, orpnpm) and prevents us from utilizing the latest features, bug fixes, and potential security patches provided in the v10 auth library.Suggested Fix
Could you please look into updating the
@google-cloud/storagedependencies to supportgoogle-auth-library@^10.0.0and cut a new release?Context
We are currently developing a GenAI project where we use Google Cloud Storage to store files and send requests. However, due to the
google-auth-libraryversion incompatibility, we are encountering a header compatibility error when making these requests. This effectively blocks our development workflow, as we cannot communicate properly with the storage service.