-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Setup to run Rails 5 builds, and fix a few issues. #1485
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
Conversation
a802727
to
980ed88
Compare
@JonRowe looks like the gemspec needs to be updated to allow Rails dependencies > 4.3 |
you should update these 3 lines here it needs accept higher version than 4.3 |
dda06d6
to
cfd92f8
Compare
380f6e7
to
6b79698
Compare
/cc @cupakromer @soulcutter This is ready for review, it doesn't fix all the Rails 5 issues but it gets the build running and fixes a couple of items. Ideally I think we'll merge this then work on other issues separately. |
0f55d6b
to
a09b8d5
Compare
Once these changes are merged into master or a separate branch, I am willing to try them out on some repos that I have ported to Rails 5. |
742501b
to
708e1c7
Compare
@jasnow this is already on a separate branch ;) |
@JonRowe -- Which branch - attempt_to_run_rails_5 or rails-5-support or something else? |
|
oh - learned something today - THANKS |
No worries :) |
@JonRowe Thanks for this. I just pushed a few more commits which fix up some more specs. I've been chatting with @cupakromer and we're going to push forward on top of this PR to get stuff up and working. From talking with @sgrif, we're going to have a rails branch called |
I've renamed this to Rails 5 support PR because I feel like it's the best effort we've got so far. |
I'd recommend just merging this and going from there, this at least gets
the build running and pushes a few fixes out. We can officially support it
later on when your branches are ready.
|
I'd rather you didn't rename it, it's not intended to be a full support,
just enough to build off on master. Smaller PRs are easier to merge, I
would have merged it myself already except I was waiting for @cupakromers
sign off.
|
Fair enough... I'll rebase it back to where it was and then merge it. It's LGTM. |
330b5bd
to
deab943
Compare
Bah you've pushed commits already, can you unpick and open a separate
PR please Sam.
|
@JonRowe I've just rebased this branch back to it's previous state. Should be good to merge on green? |
This is going to fail because travis can't install nokogiri 1.6.6.4 for some reason :( sorry @JonRowe. |
I'll see if I can work this out. |
This has already been dealt with in: #1493 which I'll merge and rebase against. |
deab943
to
8581933
Compare
Setup to run Rails 5 builds, and fix a few issues.
❤️ |
yay! |
No description provided.