Update rubocop: 1.28.1 → 1.28.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.28.1 → 1.28.2) · Repo · Changelog

Release Notes

1.28.2

Bug fixes

• #10566: Fix a false positive for Lint/AmbiguousBlockAssociation when using proc is used as a last argument. (@koic)
• #10573: Fix a false positive for Layout/SpaceBeforeBrackets when there is a dot before brackets. (@nobuyo)
• #10563: Fix Style/BlockDelimiters unexpectedly deletes block on moving comment if methods with block are chained. (@nobuyo)
• #10574: Fix a false positive for Style/SingleArgumentDig when using dig with arguments forwarding. (@ydah)
• #10565: Fix a false positive and a true negative for Style/FetchEnvVar. (@koic)

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

Commits

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

• Cut 1.28.2
• Update Changelog
• Merge pull request #10575 from nobuyo/fix-false-positive-for-layout-space-before-brackets-if-called-desugared-hash-brackets
• [Fix #10573] Fix a false positive for `Layout/SpaceBeforeBrackets` when there is a dot before bracket
• Merge pull request #10565 from ydah/fix_fetch_env_var
• Fix a false positive and a true negative for `Style/FetchEnvVar`
• Merge pull request #10576 from ydah/fix_single_argment_dig
• [Fix #10574] Fix a false positive for `Style/SingleArgumentDig` when using dig with arguments forwarding
• Merge pull request #10564 from nobuyo/fix-unexpected-block-deletion-when-style-block-delimiters-treats-comment
• Merge pull request #10567 from koic/fix_a_false_positive_for_lint_ambiguous_block_association
• Switch back the docs version
• [Fix #10566] Fix a falase positive for `Lint/AmbiguousBlockAssociation`
• [Fix #10563] Fix `Style/BlockDelimiters` unexpectedly deletes block on moving comment if methods with block are chained

↗️ regexp_parser (indirect, 2.3.0 → 2.3.1) · Repo · Changelog

Release Notes

2.3.1 (from changelog)

Fixed

• removed five inexistent unicode properties from Syntax#features
  • these were never supported by Ruby or the Regexp::Scanner
  • thanks to Markus Schirp for the report

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

Commits

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

• Release v2.3.1
• Detect and remove unsupported unicode properties
• Simplify benchmark code a bit
• Add benchmark dependency

---

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