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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
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.20.2 → 1.21.0) · Repo · Changelog
Release Notes
1.21.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
Cut 1.21.0
Update Changelog
Merge pull request #449 from koic/fix_false_positive_for_performance_redundant_block_call
[Fix #448] Fix a false positive for `Performance/RedundantBlockCall`
Merge pull request #446 from koic/support_prism
Support Prism as a Ruby parser
Tweak specs for `Performance/UnfreezeString`
Use RuboCop RSpec 2.27
Merge pull request #443 from koic/disalbe_performance_casecmp_by_default
[Fix #240] Disable `Performance/Casecmp` cop
Remove redundant `expect_no_offenses` keyword arguments
Tweak offense highlight range for `Performance/ChainArrayAllocation`
Use `Range#join` instead of generic `Parser::Source::Range.new`
Merge pull request #439 from koic/fix_a_false_positive_for_performance_chain_array_allocation
[Fix #437] Fix a false positive for `Performance/ChainArrayAllocation`
Switch back docs version to master
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