New version of rubocop-rspec (3.2.0) produced dependency conflicts #207
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.20 → ~> 3.2) · Repo · Changelog
Release Notes
3.2.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
Merge pull request #1987 from rubocop/release
Release v3.2.0
Merge pull request #1985 from rubocop/revert-unwanted-change
Merge pull request #1975 from corsonknowles/require_void_expect_acts_inside_an_example_block
Update CHANGELOG.md
Revert an change that would conceal unintentional RSpec syntax
Merge branch 'master' into require_void_expect_acts_inside_an_example_block
Merge pull request #1984 from rubocop/fixcbz
Fix an error for `RSpec/ChangeByZero` when `change (...) .by (0)` and `change (...)`, concatenated with `and` and `or`
Merge pull request #1982 from rubocop/improve-cwc
Change `RSpec/ContextWording` cop to always report an offense when both `Prefixes` and `AllowedPatterns` are empty
Merge pull request #1972 from corsonknowles/add_branch_coverage
Require VoidExpect operate inside an example block
Merge pull request #1978 from rubocop/add-issue-templete
Merge pull request #1977 from rubocop/fix-typo
Add issue templates for bug reports and feature requests
Fix typo in example_without_description_spec.rb
Merge pull request #1979 from rubocop/fix-wait
Merge pull request #1970 from corsonknowles/complete_line_coverage_for_rubocop_rspec
bundle exec rake generate_cops_documentation
Improve `confirm_documentation` task to display out-of-sync documentation
Fix problem with `Open3.popen3` where `confirm_documentation` task never finishes waiting for child processes
Complete 100 line coverage for Metadata mixin
Complete branch coverage for VoidExpect and ContextWording
Merge pull request #1974 from rubocop/fix-test-in-head
Fix a failed test in hook_spec.rb use ruby-head
Merge pull request #1967 from splattael/example-without-description-styleguide
Link related style guide for RSpec/ExampleWithoutDescription
Merge pull request #1964 from rubocop/switch-docs-version-v3.1.0
Switch docs version back
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