[ruby] Update rubocop 1.76.0 → 1.76.1 (patch) #347
Merged
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.76.0 → 1.76.1) · Repo · Changelog
Release Notes
1.76.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 23 commits:
Cut 1.76.1Update Changelog[Fix #14249] Fix false positives for `Style/RedundantArrayFlatten`Improve `expect_offense` interpolation documentationAdd new rake task to verify config references availabilityMerge pull request #14259 from koic/fix_build_error_on_windows_matrixFix build errors on Winsows matrixMerge pull request #14244 from koic/fix_false_positives_for_style_redundant_parenthesesMerge pull request #14252 from koic/workaround_ruby_lsp_0_24Workaround to avoid build error in Ruby LSP add-on test with Ruby LSP 0.24Merge pull request #14241 from viralpraxis/fix-naming-predicate-method-cop-error-on-empty-begin-method-bodyFix `Naming/PredicateMethod` cop error on empty `begin` method bodyMerge pull request #14247 from viralpraxis/fix-style-safe-navigation-invalid-autocorrection-on-colon-method-callFix `Style/SafeNavigation` cop invalid autocorrection on colon method callMerge pull request #14245 from ka8725/fix-empty-interpolationFix Lint/EmptyInterpolation for primitives[Fix #14239] Fix false positives for `Style/RedundantParentheses`Merge pull request #14237 from koic/fix_error_for_style_safe_navigation[Fix #14236] Fix an error for `Style/SafeNavigation`Merge pull request #14235 from viralpraxis/follow-up-to-pr-14234-handle-index-assignmentFollow up to #14234: handle indexed assignment[Fix #14233] Fix an error for `Style/SafeNavigation`Reset the docs versionRelease Notes
1.45.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 7 commits:
Cut 1.45.1Update ChangelogFix an error when using Parser gem with `prism_result`Suppress RuboCop's offenseSuppress RuboCop's warningRestore docs/antora.ymlCut 1.45.0Depfu 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