This repository has been archived by the owner on Jan 22, 2022. It is now read-only.
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.
We've updated a dependency and here is what you need to know:
You should probably take a good look at the info here and the test results before merging this pull request, of course.
What changed?
✳️ rubocop (0.59.2 → 0.60.0) · Repo · Changelog
Release Notes
0.60.0
New features
--safe
and--safe-auto-correct
options. (@Darhazer)--auto-gen-only-exclude
. (@Ana06, @jonas054)VersionAdded
meta data to config/default.yml when runningrake new_cop
. (@koic)Whitelist
config toRails/SkipsModelValidations
rule. (@DiscoStarslayer)Bug fixes
Rails/ReversibleMigration
when using variable assignment. (@koic, @scottmatthewman)Style/RedundantFreeze
and a false negative forStyle/MutableConstant
when assigning a regexp object to a constant. (@koic)Style/RedundantFreeze
when assigning a range object to a constant. (@koic)Rails/ReversibleMigration
when block argument is empty. (@koic)LineLength
cop for tab-indented code. (@AlexWayfer)Changes
key
option inLayout/AlignHash
cop. (@albaer)Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands