Update rubocop: 1.15.0 → 1.16.0 (minor) #31
Conversation
This file contains hidden or 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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rubocop (1.15.0 → 1.16.0) · Repo · Changelog
Release Notes
1.16.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 26 commits:
Cut 1.16Update ChangelogSupport Ruby 2.7's pattern matching for `Layout/SpaceAroundKeyword`[Fix #9839] Add `AllowedReceivers` option for `Style/HashEachMethods`[Fix #9836] Fix incorrect corrections for `Layout/HashAlignment` when a `kwsplat` node is on the same line as a `pair` node with table style.Support Ruby 2.7's pattern matching syntax for `Layout/SpaceAroundKeyword`Add new `Style/MultilineInPatternThen` copAdd new `Style/InPatternThen` copSupport auto-correction for `Style/IdenticalConditionalBranches`Add new `Lint/EmptyInPattern` copRefine offense message for `Style/WhenThen`[Fix #9822] Fix a false range for `Lint/RedundantCopDisableDirective`[Fix #9819] Fix a false negative for `Style/TopLevelMethodDefinition`Support `in` pattern syntax for `Layout/CaseIndentation`Merge pull request #9812 from koic/fix_an_error_for_layout_argument_alignmentUse `defined?` instead of `Psych::VERSION`Merge pull request #9809 from dvandersluis/issue/9793[Fix #9811] Fix an error for `Layout/ArgumentAlignment`Fix a false negative for `Layout/HashAlignment`Change `Lint/SymbolConversion` to only quote with double quotes, since `Style/QuotedSymbols` can now correct those to the correct quotes as per configuration.[Fix #9793] Add `Style/QuotedSymbols` to enforce consistency in quoted symbols.Merge pull request #9808 from koic/workaournd_for_mingw_build_errorWorkaround for mingw build errorMerge pull request #9806 from koic/fix_build_error_for_ruby_3_1_0Fix a build error for Ruby 3.1.0-devSwitch back the docs versionRelease Notes
1.7.0 (from changelog)
1.6.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 11 commits:
Cut 1.7.0Update ChangelogAdd `pattern` method for `AST::InPatternNode`Fix doc url to RubydocRevert "Improve `parent_module_name` (#177)"Add `SendNode#def_modifier` that returns the `def` node it modifies, or `nil`Improve `parent_module_name` (#177)Restore antoraCut 1.6.0Update ChangelogAdd `AST::InPatternNode` node👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.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