New version of rubocop-performance (1.21.0) produced dependency conflicts #149
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.
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:
What changed?
✳️ rubocop-performance (~> 1.7.0 → ~> 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