New version of rubocop-performance (1.21.0) produced dependency conflicts

[depfu]

We've tried to upgrade a dependency and got errors running Bundler. It looks like there is a version conflict between two or more dependencies. Depfu doesn't try to solve these, as this would mean to update more than one dependency at a time.

Please take a look at the exact failure to figure out if this is something you need to work on.

The bundler error message was:

Bundler could not find compatible versions for gem "rubocop":
  In Gemfile:
    rubocop (~> 1.10.0)

    rubocop-performance (~> 1.21.0) was resolved to 1.21.0, which depends on
      rubocop (< 2.0, >= 1.48.1)

What changed?

✳️ rubocop-performance (~> 1.7.0 → ~> 1.21.0) · Repo · Changelog

Release Notes

1.21.0

New features

• #446: Support Prism as a Ruby parser (experimental). (@koic)

Bug fixes

• #437: Fix a false positive for Performance/ChainArrayAllocation when using select with block argument after select. (@koic)
• #448: Fix a false positive for Performance/RedundantBlockCall when using block.call with block argument. (@koic)

Changes

• #240: Disable Performance/Casecmp cop by default. (@parkerfinch)

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

@​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)

[depfu]

Closed in favor of #151.

[depfu]

Closed in favor of #151.