Update rubocop 1.70.0 → 1.71.2 (minor) #262
Closed
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}
|
Closing because this update has already been applied |
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.70.0 → 1.71.2) · Repo · Changelog
Release Notes
1.71.2
1.71.1
1.71.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
3.17.0.4 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
3.3.7.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 15 commits:
Update changelog.Bump version.* parser/current: add -dev prefix to 3.4 branch (#1067)* parser/current: bump 3.2 branch to 3.2.7 (#1066)Update changelog.Update changelog.Bump version.update CI config (bump JRuby version, drop MRI 3.0 branch) (#1062)* Bump maintenance branches to 3.3.7 (#1061)Revert "* bump 3.4 branch, remove 3.0 from CI (EOL) (#1057)" (#1058)* bump 3.4 branch, remove 3.0 from CI (EOL) (#1057)* assert that version-specific checks actually run against at least one version (#1050)+ ruby34.y: reject `return` in singleton class (#1048)- Fix `ruby-parse` with a folder ending in `.rb` (#1047)Update changelog.Release Notes
1.38.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 24 commits:
Cut 1.38.0Update ChangelogUpdate to use `Node#loc?`Add `Node#loc?` to determine if a node has a given locationAdd `Node#any_block_type?` to determine if a node is either a block or numblockDisable `InternalAffairs/LocationExpression` copTest main specs against prism as well[Fix #323] Fix node captures inside of `?`, `+`, and `*` repetitionSupport node groups in `Node#each_descendant` and similar traversal methodsRemove windows-specific CI stepSimplify `internal_investigation`Add newlines between different jobsUse `bundler-cache` for `ruby/setup-ruby`Remove `TEST_QUEUE_WORKERS`Consistent naming of stepsImport RuboCop spellcheck workflowDocCI against an older RuboCop versionFix typoBetter handle `LoadError`s from prismCI against Ruby 3.4 (#351)Fix current RuboCop offenses (#350)Refactor `ArrayNode#percent_literal?`Restore docs/antora.ymlRelease Notes
3.1.4 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
Release v3.1.4CI: Add jruby and Ruby 3.4 on WindowsFix and improve handling of Skin Tone Modifiers: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