New version of rubocop-rspec (1.25.1) produced dependency conflicts #375
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-rspec ( → 1.25.1) · Repo · Changelog
Release Notes
From the Github release:
RSpec/Pendingcop when pending is used as a method name. (@Darhazer)FactoryBot/DynamicAttributeDefinedStaticallyfalse positive when using symbol proc argument for a sequence. (@tdeo)Commits
See the full diff on Github. The new version differs by 7 commits:
Merge pull request #598 from rubocop-rspec/bug-fix-releaseBump versionMerge pull request #596 from tdeo/sequence_symbol_proc_argumentAccept block_ass args in any factory methodsFix false positive in when a sequence has a symbol proc argument.Merge pull request #597 from rubocop-rspec/fix-pending-copFix false positive in cop.