Update dependencies and Rubocop configuration #175
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.
Tolken's dependencies need a facelift! I've gone over and
bundle update
d the ones that needed updating. That was pretty easy, the tests all run fine.Rubocop, however.
The old configuration was very prescriptive and onerous. I gave up on trying to get up to date with the twenty million new or renamed cops, and instead replaced the original
.rubocop.yml
with one that starts with the defaults and adds some tweaks to minimize unnecessary churn. Tests still work fine.I've also bumped the postgres version used in Travis, and opted for 13.4 which is the latest in the 13 series since 14 was released just a few weeks ago. I changed from using an explicit
rvm
key on travis to using.ruby-version
too, for greater compatibility.