New version of faraday (2.4.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		2.4.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 ( → 2.4.0) · Repo · Changelog

Release Notes

2.4.0

What's Changed

• Remove examples using extension middleware by @iMacTia in #1419
• docs: Update to 2022 by @olleolleolle in #1420
• Handle verify hostname ssl option by @kazarin in #1428
• docs link fixed by @hirotoKirimaru in #1432
• [site] Move JsonResponse middleware to response section by @jasonkarns in #1434
• Fix syntax to use correct doc link for url_encoded by @sampatbadhe in #1435
• Support Proc type for stubbed request body by @yykamei in #1436

New Contributors

• @kazarin made their first contribution in #1428
• @hirotoKirimaru made their first contribution in #1432
• @jasonkarns made their first contribution in #1434
• @sampatbadhe made their first contribution in #1435

Full Changelog: v2.3.0...v2.4.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.4.0
• Support Proc type for stubbed request body (#1436)
• Fix syntax to use correct doc link for url_encoded
• Move JsonResponse middleware to response section
• docs link fixed
• Handle verify hostname ssl option (#1428)
• docs: Update to 2022 (#1420)
• Remove examples using extension middleware

---

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)