Skip to content
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

Closed
busunkim96 opened this issue Jul 19, 2021 · 8 comments
Assignees
Labels
type: process A process-related concern. May include testing, release, or the like.

Comments

@busunkim96
Copy link
Contributor

busunkim96 commented Jul 19, 2021

While this issue is open, dependents of google-api-core, google-cloud-core. and google-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.

@busunkim96 busunkim96 added the type: process A process-related concern. May include testing, release, or the like. label Jul 19, 2021
@busunkim96 busunkim96 self-assigned this Jul 19, 2021
@busunkim96 busunkim96 changed the title google-cloud-* libraries **should not** require google-api-core>=2.x.x or google-auth>=2.x.x google-cloud-* libraries **should not** require google-api-core, google-auth or google-cloud-core >=2.x.x Jul 19, 2021
This was referenced Jul 19, 2021
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#97)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#180)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#131)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#128)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#227)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#209)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#96)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#110)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#134)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#165)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Sep 22, 2023
…versions (#189)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#48)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#234)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#81)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#156)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#13)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#143)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#183)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#205)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#200)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#101)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#109)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#55)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 21, 2023
…versions (#130)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 22, 2023
…versions (#55)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 22, 2023
…versions (#83)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 22, 2023
…versions (#93)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 22, 2023
…versions (#36)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 22, 2023
…versions (#108)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
parthea pushed a commit that referenced this issue Oct 31, 2023
…versions (#96)

Expand pins on library dependencies in preparation for these dependencies taking a new major version. See #10566.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

No branches or pull requests

5 participants