Relax version constraint for `google-cloud-storage` to avoid conflicts with both <3.0.0 and >3.0.0 libraries

[ewianda]

Description

This issue is a follow-up to #2125 and the recent change introduced in:

While this update allows google-adk to work with libraries that require google-cloud-storage >= 3.0.0, it introduces new dependency conflicts with other Google libraries that still require google-cloud-storage < 3.0.0.

Problem

• Previously, google-adk enforced google-cloud-storage <= 3.0.0, which was too restrictive for newer libraries such as firebase-admin>=7.1.0, which require google-cloud-storage >= 3.1.1.
• After the recent change, google-adk now enforces google-cloud-storage >= 3.0.0.
• However, some Google libraries still depend on google-cloud-storage < 3.0.0, creating the opposite conflict.

From reviewing the codebase, it appears that google-adk does not rely on any features that require specifically >=3.0.0, nor any features that would break with <3.0.0.

This means the strict lower bound is unnecessary and is now causing ecosystem-wide dependency friction.

Request

Please relax the version requirement for google-cloud-storage to allow compatibility with both older and newer ranges.

Summary

The current strict >= 3.0.0 constraint is too restrictive and not required for functionality. Relaxing it will restore compatibility across Google’s Python client libraries.

Thank you for considering this update!

[DeanChensj]

Hi @ewianda , do you have a version recommendation?

[ewianda]

For us apache-beam was the victim
https://github.com/apache/beam/blob/b20ccbfe3efa147ea61b32438a44a31133046b4f/sdks/python/setup.py#L479

so I am tempted to say >=2.18.2 but I don't have a reason why >2.0.0 will be a problem