Expand CI matrix to test against Faraday v0, v1 and v2
cc @jrochkind
Why
Faraday v2 was recently released, and people have started having issues with upgrading due to the sometimes pretty deep dependency trees in their applications (see https://github.com/lostisland/faraday/discussions/1358#discussioncomment-2191894).
octokit is a fairly popular gem that relies on sawyer, which unfortunately has not been updated in a while!
This PR aims to provide rolling support to all major faraday versions, from 0.x through 1.x and even the fresh new 2.x π
Once released, this will allow octokitand other gems to relax their faraday version lock and support the newest major release π
Next steps
@technoweenie @pengwynn once this is approved and merged, we'd need a new release of sawyer in Rubygems.
I'm happy for you to do so, but I could also do it myself if you provide me with 2 things:
Onwership access to the gem in Rubygems
Which versions you'd like this to be released at (0.9.0 maybe?)
Summary
cc @jrochkind
Why
Faraday v2 was recently released, and people have started having issues with upgrading due to the sometimes pretty deep dependency trees in their applications (see https://github.com/lostisland/faraday/discussions/1358#discussioncomment-2191894).
octokit
is a fairly popular gem that relies onsawyer
, which unfortunately has not been updated in a while! This PR aims to provide rolling support to all major faraday versions, from 0.x through 1.x and even the fresh new 2.x π Once released, this will allowoctokit
and other gems to relax their faraday version lock and support the newest major release πNext steps
@technoweenie @pengwynn once this is approved and merged, we'd need a new release of
sawyer
in Rubygems. I'm happy for you to do so, but I could also do it myself if you provide me with 2 things: