Bump google-cloud-storage upper bound from <3.2 to <4#1735
Open
AndreyKarasev wants to merge 1 commit intodbt-labs:mainfrom
Open
Bump google-cloud-storage upper bound from <3.2 to <4#1735AndreyKarasev wants to merge 1 commit intodbt-labs:mainfrom
AndreyKarasev wants to merge 1 commit intodbt-labs:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The upper bound for
google-cloud-storagewas pinned to<3.2, which prevents users from installing newerpatch and minor releases of the library (e.g. 3.2.x and above). This causes unnecessary dependency conflicts
for users who have other packages requiring a newer version of
google-cloud-storage.Solution
Bump the upper bound of
google-cloud-storagefrom<3.2to<4to allow all compatible 3.x releases.This follows the same pattern used for
google-cloud-bigquerywhich is already bounded at<4.0.Checklist
and understand what's expected of me
interface, etc) or this PR has already received feedback and approval from Product or DX