Rails Version Compatibility

The cluster centers on discussions about Ruby on Rails version compatibility, backwards compatibility issues, upgrades from older versions like 3.x to newer ones, and related bugs or patches in conjunction with Ruby versions.

📉 Falling 0.4x Web Development
2,242
Comments
20
Years Active
5
Top Authors
#7814
Topic ID

Activity Over Time

2007
9
2008
26
2009
87
2010
213
2011
240
2012
202
2013
525
2014
174
2015
89
2016
82
2017
80
2018
51
2019
65
2020
60
2021
71
2022
71
2023
83
2024
53
2025
58
2026
3

Keywords

e.g IMHO IMO XML rails.html github.com PR tutorial.html railslts.com rails ruby upgrade patch gem version upgrading versions bug older versions

Sample Comments

crucifiction Mar 19, 2013 View on HN

the rails community is not big on backwards compatibility, even within minor versions.

sjtgraham Mar 5, 2012 View on HN

Only for relatively new versions of Rails. The oldest version of Rails including this patch was released January 20, 2012.

sunasra Apr 19, 2019 View on HN

This is super cool. I would expect the same support for Rails after Ruby 3 release

smithcoin Dec 19, 2019 View on HN

rails still works great in 2019.

rantwasp Mar 19, 2021 View on HN

food for thought: if they have used puma (which is sort of what people have been using since 2017 when it comes to ruby/rails) would this bug have still existed?

fredrikholm Dec 26, 2022 View on HN

Rails 7 and Ruby 3.X releases most likely. I've noticed the same thing.

mrtweetyhack Dec 16, 2021 View on HN

wait. if you moving to rails 5, why not just jump to 7?

HugoDias Jun 16, 2012 View on HN

Haha I created this repository now in the morning and was already about to change the Rails version. I did not know would have an audience so quickly. I'll switch to Rails 3.2.x

jarsin Apr 19, 2019 View on HN

I think Rails had this issue by default for some time.

mishmash Nov 21, 2009 View on HN

I wonder if they're partially waiting for Rails3?