Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency faraday to v2 #3395

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 4, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
faraday (source, changelog) '~> 1.10', '>= 1.10.4' -> '~> 2.12' age adoption passing confidence

Release Notes

lostisland/faraday (faraday)

v2.12.0

Compare Source

What's Changed

New features ✨
Fixes 🐞
Misc/Docs 📄

New Contributors

Full Changelog: lostisland/faraday@v2.11.0...v2.12.0

v2.11.0

Compare Source

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 ✨
Misc/Docs 📄

New Contributors

Full Changelog: lostisland/faraday@v2.10.1...v2.11.0

v2.10.1

Compare Source

What's Changed

Full Changelog: lostisland/faraday@v2.10.0...v2.10.1

v2.10.0

Compare Source

What's Changed

This release introduces support for middleware-level default_options 🎉
You can read more about it in the docs.

New features ✨
Bug Fixes 🐞
Misc/Docs 📄

New Contributors

Full Changelog: lostisland/faraday@v2.9.2...v2.10.0

v2.9.2

Compare Source

What's Changed

Bug Fixes 🐞

New Contributors

Full Changelog: lostisland/faraday@v2.9.1...v2.9.2

v2.9.1

Compare Source

What's Changed

New features ✨
Bug Fixes 🐞
Misc/Docs 📄

New Contributors

Full Changelog: lostisland/faraday@v2.9.0...v2.9.1

v2.9.0

Compare Source

What's Changed

NOTE: This release removes support for Ruby 2.6 and 2.7, making Ruby 3.0 the minimum version.

New Contributors

Full Changelog: lostisland/faraday@v2.8.1...v2.9.0

v2.8.1

Compare Source

What's Changed

Full Changelog: lostisland/faraday@v2.8.0...v2.8.1

v2.8.0

Compare Source

What's Changed

New features ✨
Misc/Docs 📄

New Contributors

Full Changelog: lostisland/faraday@v2.7.12...v2.8.0

v2.7.12

Compare Source

What's Changed

New Contributors

Full Changelog: lostisland/faraday@v2.7.11...v2.7.12

v2.7.11

Compare Source

What's Changed

New Contributors

Full Changelog: lostisland/faraday@v2.7.10...v2.7.11

v2.7.10

Compare Source

What's Changed

New Contributors

Full Changelog: lostisland/faraday@v2.7.9...v2.7.10

v2.7.9

Compare Source

What's Changed

New Contributors

Full Changelog: lostisland/faraday@v2.7.8...v2.7.9

v2.7.8

Compare Source

What's Changed

New Contributors

Full Changelog: lostisland/faraday@v2.7.7...v2.7.8

v2.7.7

Compare Source

What's Changed

Full Changelog: lostisland/faraday@v2.7.6...v2.7.7

v2.7.6

Compare Source

What's Changed

Full Changelog: lostisland/faraday@v2.7.5...v2.7.6

v2.7.5

Compare Source

What's Changed

New Contributors

Full Changelog: lostisland/faraday@v2.7.4...v2.7.5

v2.7.4

Compare Source

What's Changed

Full Changelog: lostisland/faraday@v2.7.3...v2.7.4

v2.7.3

Compare Source

What's Changed

Fixes:

Misc:

New Contributors

Full Changelog: lostisland/faraday@v2.7.2...v2.7.3

v2.7.2

Compare Source

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: lostisland/faraday@v2.7.1...v2.7.2

v2.7.1

Compare Source

What's Changed

Full Changelog: lostisland/faraday@v2.7.0...v2.7.1

v2.7.0

Compare Source

What's Changed

New Contributors

Full Changelog: lostisland/faraday@v2.6.0...v2.7.0

v2.6.0

Compare Source

What's Changed

New features
Documentation

New Contributors

Full Changelog: lostisland/faraday@v2.5.2...v2.6.0

v2.5.2

Compare Source

What's Changed

Full Changelog: lostisland/faraday@v2.5.1...v2.5.2

v2.5.1

Compare Source

What's Changed

  • Add support for faraday-net_http adapter's latest version to make use of the new streaming API introduced in v2.5.0

Full Changelog: lostisland/faraday@v2.5.0...v2.5.1

v2.5.0

Compare Source

What's Changed

Full Changelog: lostisland/faraday@v2.4.0...v2.5.0

v2.4.0

Compare Source

What's Changed

New Contributors

Full Changelog: lostisland/faraday@v2.3.0...v2.4.0

v2.3.0

Compare Source

What's Changed

Features
Fixes
Misc

New Contributors

Full Changelog: lostisland/faraday@v2.2.0...v2.3.0

v2.2.0

Compare Source

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

v2.1.0

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

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 👏.


Configuration

📅 Schedule: Branch creation - "after 9am and before 1pm on Saturday" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented May 4, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Gemfile.lock
Fetching gem metadata from https://rubygems.org/......
Resolving dependencies...

Could not find compatible versions

Because every version of tumblr_client depends on faraday_middleware ~> 1.0
  and faraday_middleware >= 1.0.0.rc1 depends on faraday ~> 1.0,
  every version of tumblr_client requires faraday ~> 1.0.
So, because Gemfile depends on tumblr_client ~> 0.8.6
  and Gemfile depends on faraday ~> 2.9,
  version solving has failed.

@renovate renovate bot force-pushed the renovate/faraday-2.x branch 2 times, most recently from 4bdfe4b to ce1ab17 Compare May 4, 2024 02:28
Copy link
Contributor Author

renovate bot commented May 16, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Gemfile.lock
Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...

Could not find compatible versions

Because every version of tumblr_client depends on faraday ~> 1.0
  and Gemfile depends on tumblr_client ~> 0.8.6,
  faraday ~> 1.0 is required.
So, because Gemfile depends on faraday ~> 2.12,
  version solving has failed.

@trafico-bot trafico-bot bot added the 🔍 Ready for Review Pull Request is not reviewed yet label May 16, 2024
@renovate renovate bot force-pushed the renovate/faraday-2.x branch 3 times, most recently from ddfa542 to d43e313 Compare May 19, 2024 01:31
@renovate renovate bot force-pushed the renovate/faraday-2.x branch 4 times, most recently from e70f9a7 to 294fda7 Compare June 7, 2024 10:50
@renovate renovate bot force-pushed the renovate/faraday-2.x branch 3 times, most recently from 0d56817 to a74400e Compare July 8, 2024 11:38
@renovate renovate bot force-pushed the renovate/faraday-2.x branch 2 times, most recently from 65166d4 to a7cc652 Compare October 7, 2024 19:07
@renovate renovate bot force-pushed the renovate/faraday-2.x branch 5 times, most recently from c3b0c80 to 306cbf1 Compare October 26, 2024 15:10
@renovate renovate bot force-pushed the renovate/faraday-2.x branch 2 times, most recently from 6d04420 to a0fc8ea Compare October 27, 2024 14:13
@renovate renovate bot force-pushed the renovate/faraday-2.x branch 6 times, most recently from fd0b465 to ef8fa2f Compare November 9, 2024 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants