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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
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.51.0 → 1.52.0) · Repo · Changelog
Release Notes
1.52.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 40 commits:
Cut 1.52Update ChangelogServer mode: only read $stdin when -s or --stdin argument providedAdd new `Style/RedundantArrayConstructor` cop[Fix #11908] Support `AllowedReceivers` for `Style/CollectionMethods`Remove a redundant `SafeAutoCorrect: false` configMerge pull request #11907 from koic/fix_an_error_for_lint_useless_assignment[Fix #11905] Fix an error for `Lint/UselessAssignment`Merge pull request #11902 from koic/fix_a_false_positive_for_style_require_orderFix a false positive for `Style/RequireOrder`[Fix #11899] Fix an incorrect autocorrect for `Style/SingleLineMethods`Improve `Naming/VariableName`cop documentationMerge pull request #11898 from gsamokovarov/omit-parentheses-in-braced-blocksFix offences in calls inside blocks with braces for Style/MethodCallWithArgsParenthesesMerge pull request #11896 from koic/fix_false_positive_for_lint_inherit_exception[Fix #11893] Fix a false positive for `Lint/InheritException`Merge pull request #11892 from fatkodima/fix-accessor-grouping-spaceFix `Style/AccessorGrouping` to accept macros separated from accessors by spaceMerge pull request #11890 from koic/fix_a_false_negative_for_lint_redundant_safe_navigationFix a false negative for `Lint/RedundantSafeNavigation`Use `Symbol#start_with?`Merge pull request #11889 from djpowers/patch-1Merge pull request #11877 from dgollahon/remove-unused-test-setupAdd editor integration info for Helix EditorUse RuboCop Performance 1.18Tweak an offense message for `Style/EvalWithLocation`Use `RuboCop::AST::ConstNode#namespace`Tweak the doc for `Style/RescueModifier`Add new `Style/RedundantRegexpConstructor` cop[Fix #11884] Make `rubocop -V` display rubocop-factory_bot version when using it[Fix #11880] Fix a false positive for `Style/ExactRegexpMatch`Merge pull request #11881 from rubocop/dependabot/github_actions/codespell-project/actions-codespell-2Merge pull request #11879 from koic/fix_a_false_positive_for_style_select_by_regexpBump codespell-project/actions-codespell from 1 to 2Fix a false positive for `Style/SelectByRegexp` when Ruby 2.2 or lower analysisAdd the doc and tweak some specs for `Lint/MissingSuper`Remove superfluous test setupAdd new `Style/RedundantFilterChain` copAdd `ComparisonsThreshold` config option to `Style/MultipleComparison`Switch back the docs version↗️ rubocop-ast (indirect, 1.28.1 → 1.29.0) · Repo · Changelog
Release Notes
1.29.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 10 commits:
Cut 1.29.0Introduce RuboCop::Ast::MethodDispatchNode#selectorImprove docs (#265)Update .mergifyAutoformatRun rubocop's tests on oldest compatible releaseFix new cop offenseRevert "Run rubocop's tests on oldest compatible release"Run rubocop's tests on oldest compatible releaseRestore docs/antora.ymlDepfu 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