Update rubocop-performance 1.23.0 → 1.23.1 (patch) #509
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-performance (1.23.0 → 1.23.1) · Repo · Changelog
Release Notes
1.23.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 15 commits:
Cut 1.23.1
Update Changelog
Use RuboCop RSpec 3.3 for development
Bump license years to 2025
Merge pull request #483 from koic/ci_against_ruby_34
CI against Ruby 3.4
Merge pull request #480 from viralpraxis/fix-performance-squeeze-cop-error-on-frozen-ast-literal-node-value
Fix `Performance/Squeeze` cop error on frozen AST string node value
Merge pull request #481 from kyanagi/patch-1
[DOC] Fix markup of Performance/Count
Apply `rubocop --auto-gen-config`
Merge pull request #478 from viralpraxis/fix-performance-redundant-string-chars-cop-error-in-case-of-implicit-receiver
Fix `Performance/RedundantStringChars` cop error in case of implicit receiver
Suppress a RuboCop offense
Switch back docs version to master
✳️ rubocop (1.69.2 → 1.70.0) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
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