chore: loosen dependency specifications where reasonable #10
Conversation
This file contains 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
chore: update gem version
NickAnderegg
force-pushed
the
update-httparty
branch
from
f926df5 to
54c7dad
Compare
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.
This pull request makes updates to two dependencies, changing their version specification to be looser than what the original pessimistic operator allowed for:
"~> 10.0"to"~> 13.0", ">= 13.0.6". There do no appear to be any breaking changes between 10.0 and 13.0.6, according to the changelog."~> 0.13.7"to"~> 0.13", ">= 0.13.7", which allows it to be upgraded to v0.22.0 in the context of the applications that rely on this SDK.