New version of rubocop-rspec (3.5.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.61.0)

    rubocop-rspec (= 3.5.0) was resolved to 3.5.0, which depends on
      rubocop (>= 1.72.1, ~> 1.72)

What changed?

✳️ rubocop-rspec (3.0.3 → 3.5.0) · Repo · Changelog

Release Notes

3.5.0

• Don't let RSpec/PredicateMatcher replace respond_to? with two arguments with the RSpec respond_to matcher. (@bquorning)
• Fix RSpec/PredicateMatcher support for eql and equal matchers. (@bquorning)
• Pluginfy RuboCop RSpec. (@koic)

3.4.0

• Fix RSpec/SortMetadata cop to limit sorting to trailing metadata arguments. (@cbliard)
• Replace RSpec/StringAsInstanceDoubleConstant with RSpec/VerifiedDoubleReference configured to only support constant class references. (@corsonknowles)
• Fix RSpec/EmptyExampleGroup cop false positive when a simple conditional is used inside an iterator. (@lovro-bikic)

3.3.0

• Deprecate top_level_group? method from TopLevelGroup mixin as all of its callers were intentionally removed from Rubocop/RSpec. (@corsonknowles)
• Fix false positive for RSpec/EmptyMetadata for splat kwargs. (@pirj)

3.2.0

• Fix RSpec/VoidExpect to only operate inside an example block. (@corsonknowles)
• Change RSpec/ContextWording cop to always report an offense when both Prefixes and AllowedPatterns are empty. (@ydah)
• Add support for and and or compound matchers to RSpec/ChangeByZero cop. (@ydah)

3.1.0

• Add RSpec/StringAsInstanceDoubleConstant to check for and correct strings used as instance_doubles. (@corsonknowles)
• Fix false-positive for RSpec/UnspecifiedException when a method is literally named raise_exception. (@aarestad)
• Fix false-positive for RSpec/UnspecifiedException when not_to raise_error is used within a block. (@aarestad, @G-Rath)

3.0.5

• Fix false-negative and error for RSpec/MetadataStyle when non-literal args are used in metadata in EnforceStyle: hash. (@cbliard)
• Improve offense message for RSpec/IndexedLet. (@earlopain)

3.0.4

• Fix false-negative for UnspecifiedException when matcher is chained. (@r7kamura)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

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)