-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
google-cloud-* libraries should allow google-api-core
, google-cloud-core
, google-auth
>1, <3
#10565
Comments
google-api-core
, google-auth
>1, <3google-api-core
, google-cloud-core
, google-auth
>1, <3
…versions (#209) Expand pins on library dependencies in preparation for these dependencies taking a new major version. See googleapis/google-cloud-python#10565.
…versions (#210) Expand pins on library dependencies in preparation for these dependencies taking a new major version. See googleapis/google-cloud-python#10565.
Possibly useful Github searches for eyeball-verification of the pins: |
Thanks Tres! I looked through repos (using the list in the README) and it looks like expanded pins have been released almost everywhere. These were the stragglers I found:
|
I've been working today to get the Spanner release done -- it Looks like you merged the Logging one: I |
It merged this evening. |
For all
google-cloud-*
libraries that requirepython >=3.6
, expandgoogle-api-core
,google-cloud-core
andgoogle-auth
pins to>1.x.x, <3.0.0dev
.Leave a comment in the setup.py for these libraries asking library maintainers to not require >=2.x.x versions until #10566 has been closed.
Release
google-cloud-*
libraries with expanded pins.This issue can be closed when all google-cloud-* libraries have latest releases with <3.0.0dev pins.
The text was updated successfully, but these errors were encountered: