New version of faraday (2.0.0) broke the build

We've tested your project with an updated dependency and the build failed.

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	>= 1.0.0	2.0.0

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of faraday for this test run.

What changed?

✳️ faraday (>= 1.0.0 → 2.0.0) · Repo · Changelog

Release Notes

2.0.0

Faraday 2.0 🎉

The next major release is here, and it comes almost 2 years after the release of v1.0!
This release changes the way you use Faraday and embraces a new paradigm of Faraday as an ecosystem, rather than a library.
What does that mean? It means that Faraday is less of a bundled tool and more of a framework for the community to build on top of.

As a result, all adapters and some middleware have moved out and are now shipped as standalone gems 🙌!
But this doesn't mean that upgrading from Faraday 1.x to Faraday 2.0 should be hard, in fact we've listed everything you need to do in the UPGRADING.md doc.
Moreover, we've setup a new awesome-faraday repository that will showcase a curated list of adapters and middleware 😎.

This release was the result of the efforts of the core team and all the contributors, new and old, that have helped achieve this milestone 👏.

What's Changed

Begin v2 release by @iMacTia in #1297

Autoloading, dependency loading and middleware registry cleanup by @iMacTia in #1301

Move JSON middleware (request and response) from faraday_middleware by @iMacTia in #1300

Remove deprecated Faraday::Request#method by @olleolleolle in #1303

README v2 notice by @iMacTia in #1305

Remove deprecated Faraday::UploadIO by @iMacTia in #1307

[1.x] Deprecate Authorization helpers in Faraday::Connection by @iMacTia in #1306

Drop deprecated auth helpers from Connection and refactor auth middleware by @iMacTia in #1308

Add latest rubocop and use Ruby 2.6+ by @olleolleolle in #1311

Automatically refresh website Team page on commit to default branch by @iMacTia in #1315

Add Faraday 1.x examples in authentication.md docs by @iMacTia in #1320

Fix passing a URL with embedded basic auth by @iMacTia in #1324

Register JSON middleware by @mollerhoj in #1331

Retry middleware should handle string exception class name consistently by @jrochkind in #1334

Improve request info in exceptions raised by RaiseError Middleware by @willianzocolau in #1335

Remove net-http adapter and update docs by @iMacTia in #1336

update changelog 1.8.0 by @mcansky in #1338

Explain plan for faraday_middleware in UPGRADING.md by @iMacTia in #1339

Scripts folder cleanup by @iMacTia in #1340

Add Truffleruby to CI by @gogainda in #1341

Replace Hash#merge with Utils#deep_merge for connection options by @xkwd in #1343

Callable authorizers by @sled in #1345

CI: Use latest jruby-openssl release by @jbanahan in #1348

Default value for exc error by @DariuszMusielak in #1351

Don't call retry_block unless a retry is going to happen by @jrochkind in #1350

Improve documentation for v2 by @iMacTia in #1353

Remove default default_adapter (yes, you read that right) by @iMacTia in #1354

Remove retry middleware by @iMacTia in #1356

Remove multipart middleware and all its documentation and tests by @iMacTia in #1357

New Contributors

@mollerhoj made their first contribution in #1331

@jrochkind made their first contribution in #1334

@willianzocolau made their first contribution in #1335

@mcansky made their first contribution in #1338

@xkwd made their first contribution in #1343

@sled made their first contribution in #1345

@jbanahan made their first contribution in #1348

@DariuszMusielak made their first contribution in #1351

Full Changelog: v1.8.0...v2.0.0

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

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

railslove / epics