New version of faraday (2.11.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 "faraday":
  In Gemfile:
    faraday (~> 2.11)

    faraday_middleware (~> 0.12) was resolved to 0.14.0, which depends on
      faraday (< 1.0, >= 0.7.4)

What changed?

✳️ faraday (~> 0.14 → ~> 2.11) · Repo · Changelog

Release Notes

2.11.0

What's Changed

This release adds support for the ciphers SSL option (currently supported by the net_http adapter in v3.3+), as well as taking advantage of the support of chained certificates introduced in the net_http adapter in v3.2.
Also, it adds a new ParallelManager#execute interface that improves on the existing one and makes it easier for adapters to support parallel requests. This is currently used by the async-http adapter.

New features ✨

• Add support for a new ParallelManager#execute method. by @iMacTia in #1584
• Add ciphers attribute to SSLOptions by @womblep in #1582

Misc/Docs 📄

• Opt-in for MFA requirement explicitly by @tagliala in #1580
• Fix typos by @tagliala in #1585

New Contributors

• @tagliala made their first contribution in #1580
• @womblep made their first contribution in #1582

Full Changelog: v2.10.1...v2.11.0

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

Commits

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

• Version bump to 2.11.0
• Allow `faraday-net_http` 3.3.x
• Add ciphers attribute to SSLOptions (#1582)
• Fix typos (#1585)
• Opt-in for MFA requirement explicitly (#1580)
• Add support for a new `ParallelManager#execute` method. (#1584)
• Update faraday-net_http requirement from >= 2.0, < 3.2 to >= 2.0, < 3.3 (#1579)

---

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)