Relax dev dependencies - #361
Merged
Merged
Conversation
Don't pin development dependencies to specific (old) versions. It could make sense to change several dependencies from `~>` to `>=`. And _maybe_ keep `rspec` and `webmock` with `~>`. But, at least for gem development, I've found that's usually much more hassle than it's worth.
This is how `bundle gem` has generated new gems for a while now.
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
2 participants
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.
Don't pin development dependencies to specific (old) versions. There appear to be some minor incompatibilities with ruby 4.0 and some of the older development dependencies.
It could make sense to change several dependencies from
~>to>=. And maybe keeprspecandwebmockwith~>. But, at least for gem development, I've personally found that's usually much more hassle than it's worth.