In #946 (included in the v3.0.0 release), the version of faraday that this gem depends on was bumped to ~> 1.0. So in order to upgrade our app to the 3.x release series of this gem, we'd also have to upgrade the version of faraday that our app depends on. Unfortunately, we have a number of other gems that require a pre-1.0 version of faraday. I've seen other gems (e.g., twilio-ruby, restforce) use a looser constraint by allowing versions between 0.9 and 2.0. Can we do something similar here? Or does this gem depend on something in faraday 1.x that makes that idea a nonstarter?
In #946 (included in the v3.0.0 release), the version of faraday that this gem depends on was bumped to
~> 1.0. So in order to upgrade our app to the 3.x release series of this gem, we'd also have to upgrade the version of faraday that our app depends on. Unfortunately, we have a number of other gems that require a pre-1.0 version of faraday. I've seen other gems (e.g., twilio-ruby, restforce) use a looser constraint by allowing versions between 0.9 and 2.0. Can we do something similar here? Or does this gem depend on something in faraday 1.x that makes that idea a nonstarter?