-
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 not** require google-api-core
, google-auth
or google-cloud-core
>=2.x.x
#10566
Labels
type: process
A process-related concern. May include testing, release, or the like.
Comments
busunkim96
added
the
type: process
A process-related concern. May include testing, release, or the like.
label
Jul 19, 2021
busunkim96
changed the title
google-cloud-* libraries **should not** require
google-cloud-* libraries **should not** require Jul 19, 2021
google-api-core>=2.x.x
or google-auth>=2.x.x
google-api-core
, google-auth
or google-cloud-core
>=2.x.x
This was referenced Jul 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While this issue is open, dependents of
google-api-core
,google-cloud-core
. andgoogle-auth
should preserve>1, <3
pins on these packages.This is to prevent diamond dependency conflicts for users using multiple libraries. A more detailed rationale is provided in this document.
If you believe you need to begin requiring
>=2.x.x
versions of these libraries, please comment here or reach out before releasing your library.This issue is currently expected to be closed 3 months (90 days) after all
google-*
packages have been released with expanded pins (see #10565), however the specific amount of time is under discussion.The text was updated successfully, but these errors were encountered: