Update rubocop → 1.56.4 (unknown) #187
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rubocop (1.56.3 → 1.56.4) · Repo · Changelog
Release Notes
1.56.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 29 commits:
Cut 1.56.4Update ChangelogMerge pull request #12222 from koic/fix_a_false_positive_for_layout_empty_line_after_guard_clauseMerge pull request #12220 from koic/fix_an_incorrect_autocorrect_for_disable_uncorrectable_option[Fix #12221] Fix a false positive for `Layout/EmptyLineAfterGuardClause`[Fix #12208] Fix an incorrect autocorrect for the `--disable-uncorrectable` optionMerge pull request #12218 from koic/fix_a_false_positive_for_lint_ordered_magic_comments[Fix #12213] Fix a false positive for `Lint/OrderedMagicComments`Disable `RSpec/FilePath` to resolve build errorMerge pull request #12215 from koic/update_the_doc_of_style_return_nil[Docs] Update the doc for `Style/ReturnNil`Use `safe_navigation?` instead of custom methodFix duplicate contributor names when generating changelogMerge pull request #12206 from koic/fix_an_incorrect_autocorrect_for_style_operator_method_callFix an incorrect autocorrect for `Style/OperatorMethodCall`Merge pull request #12207 from koic/fix_an_error_for_style_operator_method_call[Fix #12205] Fix an error for `Style/OperatorMethodCall`Merge pull request #12204 from koic/support_autocorrect_for_internal_affairs_example_descriptionSupport autocorrect for `InternalAffairs/ExampleDescription`Add a project spec to prevent error when running `rake changelog:merge`Merge pull request #12203 from koic/fix_an_incorrect_autocorrect_for_lint_safe_navigation_chainFix an incorrect autocorrect for `Lint/SafeNavigationChain`Merge pull request #12202 from ydah/fix-incorrect-autocorrect-redundant-conditionalFix an incorrect autocorrect for `Style/RedundantConditional` when unless/else with boolean results[Fix #12199] Fix false negatives for `Layout/MultilineMethodCallIndentation`Merge pull request #12200 from ydah/fixUselessMessageAssertionFix an error for `InternalAffairs/UselessMessageAssertion` when empty fileMake `Style/CollectionMethods` aware of `collect_concat`Cut 1.56.3Depfu 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