feat: switch to Faraday 2 #10
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dmitrytrager
force-pushed
the
feat/faraday-2.0
branch
from
d7a5957 to
10731b7
Compare
dmitrytrager
force-pushed
the
feat/faraday-2.0
branch
from
10731b7 to
89b6c77
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to proceed with further updates, we need our dependencies to include Faraday v2 instead of Faraday v1.
This gem does not use middlewares that were previously bundled and now removed. Base class
Faraday::Middlewareis still available. SoErrorMiddlewarecan work as before.Faraday 2 required Ruby older than 3. Thus, support for 2.7 should be dropped, but we can add 3.4 now. Upcoming
pandaversions won't break Ruby support, I believe, so we could rename currentmainbranch to0.5and keep it, while using this branch as a newmain.