Leave pessimistic gem versions alone, no matter the requested constraint #17
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
|
A mere 7 years after the pull request was opened, and I'm now addressing this. Seriously, apologies for going AWOL, and thank you for the PR. It needs to be merged with some recent changes to remove the trollop gem, so I'm going to merge to a separate branch, handle and check the merge, then bring it into master. |
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.
When I ran
pessimizeon a Gemfile containing prerelease gem versions they got stripped out and later calls tobundlewould fail. This attempts to leave those versions alone while still converting to a pessimistic constraint so later gem updates are picked up.