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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rubocop (0.91 → 1.22.1) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 14 commits:
Cut 1.22.1
Update Changelog
[Fix #10145] Update `Style/SelectByRegexp` to ignore cases where the receiver appears to be a hash.
[Fix #10148] Fix `Style/QuotedSymbols` handling escaped characters incorrectly.
Fix inconsistent capitalization of `RuboCop`.
Clarify documentation for `Style/QuotedSymbols`.
Refine offense highlight range for `Style/RedundantArgument`
Merge pull request #10146 from koic/fix_an_error_for_lint_require_relative_self_path
Merge pull request #10141 from dvandersluis/issue/10140
[Fix #10143] Fix an error for `Lint/RequireRelativeSelfPath`
Minor update to changelog and release notes.
[Fix #10140] Fix false positive for `Layout/DotPosition` when a heredoc receives a method on the same line as the start sigil in `trailing` style.
Tweak a changelog entry
Switch back the docs version
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