Update rubocop 1.54.1 → 1.54.2 (patch)

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.54.1 → 1.54.2) · Repo · Changelog

Release Notes

1.54.2

Bug fixes

• #12043: Fix a false negative for Layout/ExtraSpacing when some characters are vertically aligned. (@koic)
• #12040: Fix a false positive for Layout/TrailingEmptyLines to prevent the following incorrect autocorrection when inspecting the % form string %\n\n. (@koic)
• #1867: Fix an error when AllCops:Exclude is empty in .rubocop.yml. (@koic)
• #12034: Fix invalid byte sequence in UTF-8 error when using an invalid encoding string. (@koic)
• #12038: Output the "server restarting" message to stderr. (@knu)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 21 commits:

• Cut 1.54.2
• Update Changelog
• [Doc] Fix an incorrect link in the LSP doc
• Fix a false negative for `Layout/ExtraSpacing`
• Merge pull request #12040 from koic/fix_a_false_positive_for_layout_trailing_empty_lines
• [Doc] Add a configuration example of nvim-lspconfig to the LSP doc
• Use `AST::Node#call_type?`
• Fix a false positive for `Layout/TrailingEmptyLines`
• Merge pull request #12038 from knu/output_restarting_message_to_stderr
• Output the "server restarting" message to stderr
• Merge pull request #12035 from koic/fix_an_error_when_using_an_invalid_encoding_string
• Merge pull request #12032 from koic/fix_an_error_when_allcops_exclude_is_empty
• [Fix #12034] Fix an error when using an invalid encoding string
• [Doc] Add a configuration example of Neovim to the LSP doc
• [Doc] Tweak the Integration with Other Tools doc
• Remove a redundant return condition for `Style/Semicolon`
• [Fix #1867] Fix an error when `AllCops:Exclude` is empty in .rubocop.yml
• Tweak offense range highlight for `Naming/HeredocDelimiterNaming`
• Merge pull request #12031 from lucthev/return-nil-typo
• Fix typo in Style/ReturnNilInPredicateMethodDefinition docs
• 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

@​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)