Skip to content

[ruby] New version of rubocop-rspec (3.8.0) produced dependency conflicts #147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[ruby] New version of rubocop-rspec (3.8.0) produced dependency conflicts #147

wants to merge 1 commit into from

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Nov 13, 2025

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.8.0) was resolved to 3.8.0, which depends on
      rubocop (~> 1.81)

What changed?

✳️ rubocop-rspec (~> 2.26.1 → ~> 3.8.0) · Repo · Changelog

Release Notes

3.8.0

  • Add new cop RSpec/LeakyLocalVariable. (@lovro-bikic)
  • Bump RuboCop requirement to +1.81. (@ydah)
  • Fix a false positive for RSpec/LetSetup when let! used in outer scope. (@ydah)
  • Fix a false positive for RSpec/ReceiveNever cop when allow(...).to receive(...).never. (@ydah)
  • Fix detection of nameless doubles with methods in RSpec/VerifiedDoubles. (@ushi-as)
  • Improve an offense message for RSpec/RepeatedExample cop. (@ydah)
  • Let RSpec/SpecFilePathFormat leverage ActiveSupport inflections when configured. (@corsonknowles, @bquorning)

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

Commits

See the full diff on Github. The new version differs by 32 commits:

Depfu Status

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)

@depfu depfu bot added the dependencies label Nov 13, 2025
@depfu depfu bot mentioned this pull request Nov 13, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant