You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
We won't update sentry-raven anymore except for very critical issues (like a security issue). So I recommend you to migrate to the new SDK. All the extra features/bug fixes aside, the sentry-ruby-core gem has a no requirement and can potentially fit your app in this condition. Here's the migration guide.
Sorry, I'm a little confused. Both the old sentry-raven and the new sentry-rubygems require version >= 1.0 of faraday, right? So if I try to migrate from sentry-raven to sentry-ruby (which is what I'm trying to do), I'll need to upgrade faraday to 1.x as well which isn't compatible with our other dependencies. There are newer versions of those gems that support version >= 1.0 of faraday but that means we'll have to update all of them (plus sentry-ravenandfaraday) in one go which makes for a very large surface area for bugs to crop up. Ideally I could update each one individually and then, once we've verified that no bugs have been introduced, we could update faraday separately.
Again, loosening the version constraint to support 0.9.x only works if you're sure that sentry-ruby doesn't rely on anything in the 1.x series of faraday. Do you know if that's the case?
Sorry I should've stated this clearer, we have a gem called sentry-ruby-core that has no dependency version requirements. sentry-ruby is a wrapper around it with version requirements.
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?The text was updated successfully, but these errors were encountered: