dude icon indicating copy to clipboard operation
dude copied to clipboard
verified publisher icon npupko

Update faraday requirement from ~> 1.1 to >= 1.1, < 3.0

Open dependabot[bot] opened this issue 3 years ago • 0 comments

Updates the requirements on faraday to permit the latest version.

Release notes

Sourced from faraday's releases.

v2.7.4

What's Changed

Full Changelog: https://github.com/lostisland/faraday/compare/v2.7.3...v2.7.4

v2.7.2

What's Changed

ATTENTION

Rename Faraday::Logger::Formatter#error (#1468) is potentially a breaking change IF you've created a custom Faraday::Logging::Formatter implementing the new error method introduced in v2.7.0.

We've decided to rollout this change in a fix version anyway because the name of the method was potentially causing infinite loop issues, and because the feature was very recently released.

This should not be impacting you otherwise and you can safely upgrade.

New Contributors

Full Changelog: https://github.com/lostisland/faraday/compare/v2.7.1...v2.7.2

v2.7.1

What's Changed

Full Changelog: https://github.com/lostisland/faraday/compare/v2.7.0...v2.7.1

v2.7.0

What's Changed

New Contributors

Full Changelog: https://github.com/lostisland/faraday/compare/v2.6.0...v2.7.0

v2.6.0

What's Changed

New features

... (truncated)

Changelog

Sourced from faraday's changelog.

Faraday Changelog

The changelog has moved!

This file is not being updated anymore. Instead, please check the Releases page.

2.2.0 (2022-02-03)

  • Reintroduce the possibility to register middleware with symbols, strings or procs in #1391

2.1.0 (2022-01-15)

2.0.1 (2022-01-05)

2.0.0 (2022-01-04)

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

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependabot[bot] avatar Jan 23 '23 03:01 dependabot[bot]