New version of faraday (2.7.0) produced dependency conflicts

[depfu]

We've tested your project with an updated dependency and got errors while installing the dependencies.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
faraday	>= 0.9	2.7.0

Unfortunately, the build failed while installing dependencies. This means that while the new version is within the specified range, a version conflict between two or more packages will prohibit this version from being installed.

As this breaks fresh installs of your package, we've left this pull request open for you to investigate.

What changed?

✳️ faraday (>= 0.9 → 2.7.0) · Repo · Changelog

Release Notes

2.7.0

What's Changed

• GitHub Workflows security hardening by @sashashura in #1451
• Remove unnecessary require 'pp' by @iMacTia in #1457
• Convert self[key] to a String with #<< on #add_parsed by @yykamei in #1459
• Allow logging of errors raised in adapters or other middleware by @epaew in #1460

New Contributors

• @sashashura made their first contribution in #1451
• @epaew made their first contribution in #1460

Full Changelog: v2.6.0...v2.7.0

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

Commits

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

• Version bump to 2.7.0
• Update documents for response logger middleware.
• Formatter: make errors' logging controllable.
• Faraday::Logging::Formatter#error: Prevent NoMethodError when received anything other than Faraday::Error.
• Feature: Allows logging of errors that raised in adapter or other middleware.
• Utils::Headers: Convert `self[key]` to a String with `#<<` on `#add_parsed` (#1459)
• Remove unnecessary `require 'pp'` (#1457)
• GitHub Workflows security hardening (#1451)

---

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 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)