Lock down development dependency versions #355
Merged
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
Because we don't check in `Gemfile.lock`, it's good to lock these down in our `gemspec` file. This makes sure the build stays consistent if, say, there's a major breaking release of RSpec, or once we've added Rubocop to the build we don't want it to randomly fail every time they add new rules.
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.
Because we don't check in
Gemfile.lock, it's good to lock these downin our
gemspecfile. This makes sure the build stays consistent if,say, there's a major breaking release of RSpec, or once we've added
Rubocop to the build we don't want it to randomly fail every time they
add new rules.