-
Notifications
You must be signed in to change notification settings - Fork 122
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
Faraday dependency causing issues #31
Comments
huh, yeah, we can certainly relax it! |
+1 |
Any update on this? I can't update my bundle right now in a straightforward manner without this breaking dependency issue. |
* adding .group(), .page(), and .screen() calls * relaxing faraday dependency, fixes #31
Yep, just relaxed from the latest version! |
Bundler could not find compatible versions for gem "faraday":
|
Also having the same problem as @mikeatlas |
Might need to open a new ticket...
|
hey guys, yeah the problem seems to be that it's probably worth dropping all of these deps and just going with core libraries, since we're not doing anything fancy. making json requests shouldn't be too difficult |
The current gemspec won't work in bundler for this reason: Bundler could not find compatible versions for gem "faraday":
|
yeah, that's thanks to |
:( did you get a chance to take a look at this? Somehow our production app has dropped back to analytics-ruby 0.0.1 and I can't get any recent version running because lots of other gems now depend on faraday 0.9 ¯_(ツ)_/¯ |
@jongd yep, just removed faraday with 1.0.0. if you give it a spin, please let me know if you run into any problems! |
Hero, thanks so much. |
working for me now. thanks |
Hi,
the dependency on Faraday is declared in such a way that it is causing problems:
spec.add_dependency 'faraday', ['>= 0.8', '< 0.10']
Faraday is now on 0.9 but users of analytics-ruby cannot update as it conflicts with this requirement. IMO unless there is a specific known incompatibility with 0.10 (impossible, since it is not released yet), it's inappropriate to exclude it in this way. '>= 0.8' should be sufficient.
The text was updated successfully, but these errors were encountered: