Update google-cloud-storage requirement #15
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.
Hi there! Upgradvisor has identified that one of your repository’s dependencies has a newer version available, and we recommend you upgrade.
Your code currently pins
google-cloud-storage==1.0.0when google-cloud-storage1.35.0is available. The attached graph shows the dependency path of your repository relative togoogle-cloud-storage. Your code is shown in green (each node is a method), and your code callinggoogle-cloud-storageis shown in orange. Changes between version1.35.0and1.43.0are shown as starred.The major changes from the dependecy are:
_DEFAULT_STORAGE_HOST, butbudgetmlwon’t be affected because it didn’t change or redefine it;GETandPOSTmethods, in which only modifies that dependency’s inner behavior that won’t affect the application code.Nonecheck in_bucket_arg_to_bucket, which is not applicable tobudgetmlbecause it instantiates a not-None object.Upgradvisor is a research project from Columbia University’s RCS lab. Our goal is to provide meaningful information for developers (like you) on how to upgrade their software dependencies. If you have any questions or feedback please reach out to the Upgradvisor team at [email protected]
