Update rubocop-rails 2.24.1 → 2.26.0 (minor) #3450
Closed
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-rails (2.24.1 → 2.26.0) · Repo · Changelog
Release Notes
2.26.0
2.25.1
2.25.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.
✳️ rubocop (1.65.0 → 1.65.1) · Repo · Changelog
Release Notes
1.65.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 41 commits:
Cut 1.65.1
Update Changelog
Merge pull request #13083 from Earlopain/false-positive-global-std-stream
Fix false positive for `Style/GlobalStdStream` for namespaced constants
Clarify docs in Naming/PredicateName
Add a validate_config for Naming/PredicateName
Merge pull request #13079 from koic/fix_incorrect_autocorrect_for_naming_rescued_exceptions_variable_name
Merge pull request #13081 from fatkodima/zero_length_predicate-false-positive
Fix a false positive for `Style/ZeroLengthPredicate` when using safe navigation and non-zero comparison
[Fix #13076] Fix an incorrect autocorrect for `Naming/RescuedExceptionsVariableName`
Merge pull request #13075 from koic/mark_broken_on_prism_for_broken_specs_for_ruby34_with_prism
Mark `broken_on: :prism` for broken specs using Ruby 3.4.0dev with Prism
Enable branch coverage
[Fix #11438] Explicitly load `fileutils` before calculating `before_us`
[Doc] Tweak the doc of `Layout/AssignmentIndentation`
Merge pull request #13071 from Earlopain/bump-simplecov
Bump `simplecov`
Merge pull request #13069 from Earlopain/regexp_parser_cruft
Drop `regexp_parser` < 2.0 compatibility code
Merge pull request #13066 from koic/fix_an_error_for_lint_useless_assignment_cop
[Fix #13065] Fix an error for `Lint/UselessAssignment`
Merge pull request #13062 from Earlopain/invertible-unless-empty-braces
Fix an error for `Style/InvertibleUnlessCondition` when using empty parenthesis as condition
Remove an unused private method
[Docs] Fix code example for `Lint/ShadowingOuterLocalVariable`
[Docs] Consistent usage of `@example`
Clarify how to specify the number of parallel processes
Fix a typo
[Docs] Tweak the v1 Upgrade Notes
[Fix #13044] Fix false negatives for `Lint/ImplicitStringConcatenation`
[Fix #13051] Fix an error for `Lint/FloatComparison`
Merge pull request #13043 from koic/fix_false_positives_for_lint_useless_assignment
Merge pull request #13047 from m11o/feature/fix-warning
Use `support_autocorrect?` class method.
[Fix #13041] Fix false positives for `Lint/UselessAssignment`
Merge pull request #13040 from koic/tweak_autocorrect_for_style_sole_nested_conditional
Tweak autocorrect for `Style/SoleNestedConditional`
Use `RuboCop::AST::Node#equals_asgn?`
[Docs] Tweak the doc of `Style/EvalWithLocation`
Remove an unused private method
Reset the docs version
Commits
See the full diff on Github. The new version differs by 10 commits:
v1.26.3
Merge pull request #351 from y-yagi/ensure_not_to_use_old_concurrent-ruby
Ensure not to use old `concurrent-ruby`
v1.26.2
Revert "Revert "Merge pull request #348 from y-yagi/use_available_processor_count""
v1.26.1
Revert "Merge pull request #348 from y-yagi/use_available_processor_count"
v1.26.0
Merge pull request #348 from y-yagi/use_available_processor_count
Use cgroups aware processor count by default
Release Notes
3.3.4.1 (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:
Update changelog.
Bump version.
- Fix errros in the ascii specs of RuboCop (#1037)
Update changelog.
Update changelog.
Bump version.
* Bump 3.2 branch to 3.2.5. (#1036)
- builder.rb: catch encoding errors when parsing invalid encoding regexp (#1033)
* Bump Racc to 1.8.1 (#1031)
Suppress Ruby 3.4's warning (#1028)
Update changelog.
Release Notes
1.32.1 (from changelog)
1.32.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 23 commits:
Cut 1.32.1
Update Changelog
Mark `RuboCop::AST::EnsureNode` as being in a void context.
Fix readme CI badge (#308)
Move test `Node#used?` predicate method definition
Restore docs/antora.yml
Cut 1.32.0
Update Changelog
Add `RuboCop::AST::RationalNode`
Remove `Range#minmax` refinement (#307)
Link the node pattern debugger in docs
[Docs] Update the doc of Node Types
Suppress RuboCop offense
Lift the deprecation from `ArrayNode#each_value`
Move `rubocop:disable` comments out of documentation
Define `recursive_*literal?` methods using macro
Bump paambaati/codeclimate-action from 5.0.0 to 8.0.0 (#294)
Fix a build error (#296)
Fix an error when running RuboCop RSpec 3.0
Suppress RuboCop offenses
Use Prism 0.28+ for development (#292)
This has been failing for ages, remove for now
Restore docs/antora.yml
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