Update rubocop 1.56.4 → 1.57.0 (minor) #165
Closed
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rubocop (1.56.4 → 1.57.0) · Repo · Changelog
Release Notes
1.57.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 41 commits:
Cut 1.57
Update Changelog
[Fix #12076] Explicitly require fileutils in RuboCop::Server::Cache
[Fix #12259] Fix an error for `Lint/MixedCaseRange`
Fix an error for `Style/RedundantDoubleSplatHashBraces`
[Fix #12257] Make `Style/RedundantDoubleSplatHashBraces` aware of `merge`
[Fix #12249] Fix a false positive `Style/IdenticalConditionalBranches`
Merge pull request #12255 from ydah/followup-12176
Remove redundant true/false returns
Merge pull request #12254 from joesiewert/empty-block-text
Edit empty block overview text
Merge pull request #12253 from knu/accept_empty_string_literal_interpolated_in_words_literal
Update `Lint/LiteralInInterpolation` to accept an empty string literal interpolated in %W[]/%I[]
Merge pull request #12247 from koic/fix_false_negatives_for_style_redundant_parentheses
Merge pull request #12250 from koic/mark_lint_redundant_require_statement_as_unsafe_autocorrect
Fix false negatives for `Style/RedundantParentheses`
Mark `Lint/RedundantRequireStatement` as unsafe autocorrect
Remove an unused `include Alignment`
Merge pull request #12234 from koic/enhance_style_format_string_autocorrection
Enhance `Style/FormatString`'s autocorrection
Fix a link address for #12246
Make `Lint/RedundantSafeNavigation` aware of constant receiver
[Fix #12244] Fix a false negative for `Lint/Debugger`
[Fix #12198] Fix an error for flip-flop with beginless or endless ranges
Merge pull request #12240 from koic/fix_a_false_negative_for_metrics_module_length
[Fix #12231] Fix a false negative for `Metrics/ModuleLength`
Fix a build error
Merge pull request #12238 from koic/fix_an_error_for_style_nested_ternary_operator
[Fix #12237] Fix an error for `Style/NestedTernaryOperator`
Merge pull request #12235 from aboutsource/feature/auto_parallel_with_explicit_config
Enable auto parallel inspection when config file is specified
[Docs] Tweak docs for `Metrics/BlockLength` and `Metrics/ClassLength`
Tweak autocorrection for `Style/RedundantBegin`
[Fix #12226] Fix false positives for `Layout/MultilineMethodCallIndentation`
Add new `Style/SingleLineDoEndBlock` cop
Fix false negatives for `Style/MultilineBlockChain`
[Fix #12097] Mark unsafe autocorrect for `Style/ClassEqualityComparison`
Make `Style/RedundantFilterChain` aware of `select.present?`
[Fix #12128] Make `Style/GuardClause` aware of `define_method`
[Fix #12210] Mark `Style/RedundantFilterChain` as unsafe autocorrect
Switch back the docs version
Release Notes
2.8.2 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 9 commits:
Release v2.8.2
Fix rubocop
Mirror Onigmo quirk for escaped number chains ...
Update README.md
Test on 3.2 explicitly, now that head is 3.3
Omit docs from bundled gem
Declutter CHANGELOG a bit
Add author in gemspec
Test token map against current syntax
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