Ruby, Rails, and All gems out of date

Question

Ruby, Rails, and All gems out of date

Closed this issue 6 years ago · 6 comments

Like the title says, pretty much everything out of date. Ruby 2.1 is not even supported anymore, 2.4.0 is the latest. Same with rails, 4.1 is not supported, only 5.0 and 4.2 are.

I can take a look at upgrading but I don't know what the limitation of CI/Heroku are for these things. Additionally, the move from 4.1 => 5 might be a not-so-small undertaking in my experience, it might make more sense to stay on ~4 for now.

Answer 1 · 2017-01-23T22:16:29.000Z

Already found an active rails bugs with ruby 2.4.0 & Rails 4.2.0.

I think the Integer unification is going to take a while to fix for not only rails but every active record adapter.

Backing off to ruby 2.3.3 for now..

Answer 2 · 2017-01-23T22:23:42.000Z

For now, let's target Ruby 2.3.x and Rails 4.2.x.

Answer 3 · 2017-01-23T22:40:54.000Z

I have a green rake on a branch here. Waiting on the first PR to be merged in then I'll create this one (otherwise you'd see the commit history from the first PR in this PR).

Answer 4 · 2017-01-23T22:41:39.000Z

I've done 4.1 to 4.2 and it's not that bad. I do agree to 5 is a big step. The only thing I can think of is if we use respond with or not. I don't think we do. Heroku should handle the latest Ruby, so you probably won't need to worry much about that upgrade. We're not doing anything particularly crazy in this repo either.

…

On Mon, Jan 23, 2017 at 4:51 PM Alex Hall ***@***.***> wrote: Like the title says, pretty much everything out of date. Ruby 2.1 is not even supported anymore, 2.4.0 is the latest. Same with rails, 4.1 is not supported, only 5.0 and 4.2 are. I can take a look at upgrading things but I don't know what the limitation of CI/Heroku are for these things. Additionally, the move from 4.1 => 5 might be a not-so-small undertaking in my experience, it might make more sense to stay on ~4 for now. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#55>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLLK45WHYZ50tNlwiepqwYB0ITIt5a8ks5rVSDpgaJpZM4Lrlxs> .

Answer 5 · 2017-01-23T22:46:13.000Z

Good stuff in your WIP.

…

On Mon, Jan 23, 2017 at 5:41 PM Stephen Bussey ***@***.***> wrote: I've done 4.1 to 4.2 and it's not that bad. I do agree to 5 is a big step. The only thing I can think of is if we use respond with or not. I don't think we do. Heroku should handle the latest Ruby, so you probably won't need to worry much about that upgrade. We're not doing anything particularly crazy in this repo either. On Mon, Jan 23, 2017 at 4:51 PM Alex Hall ***@***.***> wrote: Like the title says, pretty much everything out of date. Ruby 2.1 is not even supported anymore, 2.4.0 is the latest. Same with rails, 4.1 is not supported, only 5.0 and 4.2 are. I can take a look at upgrading things but I don't know what the limitation of CI/Heroku are for these things. Additionally, the move from 4.1 => 5 might be a not-so-small undertaking in my experience, it might make more sense to stay on ~4 for now. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#55>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLLK45WHYZ50tNlwiepqwYB0ITIt5a8ks5rVSDpgaJpZM4Lrlxs> .

Answer 6 · 2017-01-23T23:02:12.000Z

PR Submitted: #57