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
Arel version dependency breaks gems #16063
Comments
|
If you trying against rails master, add the arel from master too. Something like i did here. |
|
What @seuros said, if you want to test rails master make sure you include arel master too, just like we are doing. |
|
This is a transitive dependency though. Awkward. |
|
Awkward indeed... but I think it's really in bundler's problem-space: some way for us to say "hey, if you're pulling us from git, and you don't have a better idea, you might want to try as a source for arel". The problems (and potential security implications) of such a scheme are multitudinous, and likely why it's not supported. /ping @indirect in case he has any brilliant suggestions |
|
Some options: combine repos, modify the bootstrap script to check out arel, create a separate Gemfile for rails master, release prerelease gems every time there's a breaking dependency change, put it in the readme in big letters. There's no magical automatic solution to breaking dependency changes, but you can solve them by solving them. :P On Sat, Jul 5, 2014 at 10:29 AM, Matthew Draper notifications@github.com
|


In f200383, arel's version got bumped. But since 6.0 hasn't been released yet, any gem that tries to integration test against Rails master straight-up fails:
https://travis-ci.org/steveklabnik/active_model_serializers/jobs/29204778
https://travis-ci.org/drapergem/draper/jobs/29070352
etc.
This means that getting early bug reports about stuff in master that breaks gems that depend on Rails won't happen.
The text was updated successfully, but these errors were encountered: