New version of rspec-rails (6.1.1) 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 "activesupport":
  In Gemfile:
    travis (~> 1.10) was resolved to 1.11.1, which depends on
      gh (~> 0.13) was resolved to 0.18.0, which depends on
        activesupport (~> 5.0)

    rspec-rails (~> 6.1) was resolved to 6.1.1, which depends on
      activesupport (>= 6.1)

Bundler could not find compatible versions for gem "faraday":
  In Gemfile:
    travis (~> 1.10) was resolved to 1.11.1, which depends on
      gh (~> 0.13) was resolved to 0.15.1, which depends on
        faraday (~> 0.8)

    travis (~> 1.10) was resolved to 1.11.1, which depends on
      faraday (~> 1.0)

What changed?

✳️ rspec-rails (~> 5.0 → ~> 6.1) · Repo · Changelog

Release Notes

6.1.1 (from changelog)

Full Changelog

Bug Fixes:

• Improved deprecation message for RSpec::Rails::Configuration.fixture_paths (Benoit Tigeot, #2720)
• Fix support for namespaced fixtures in Rails 7.1. (Benedikt Deicke, #2716)

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

Commits

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

• v6.1.1
• Merge pull request #2725 from rspec/dependabot/github_actions/actions/dependency-review-action-4
• Merge pull request #2726 from rspec/update-rspec-rails-build
• Update bug_report.md
• Fix diff link
• Tweak feature request template
• Changelog for #2716
• Merge pull request #2721 from rspec/add-namespaced-fixture-spec
• Changelog for #2720
• Merge pull request #2720 from rspec/more-details-to-change-fixture-paths
• Merge pull request #2719 from rspec/refactor-generator-specs

---

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)