[ruby] New version of rubocop-performance (1.26.1) produced dependency conflicts #27
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.20.2 → ~> 1.26.1) · Repo · Changelog
Release Notes
1.26.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 9 commits:
Cut 1.26.1Update ChangelogMerge pull request #521 from Earlopain/disable-bigdecimal[Fix #520] Disable `Performance/BigDecimalWithNumericArgument` by defaultMerge pull request #518 from koic/fix_false_positives_for_performance_redundant_string_chars[Fix #517] Fix false positives for `Performance/RedundantStringChars`Tweak bug report templateSuppress RuboCop's offenseSwitch back docs version to masterDepfu 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