# Where Can i know for which version of ruby is officially tested for a particular version of rails **URL:** \ **Category:** rubyonrails-docs\ **Tags:** ruby-language\ **Created:** [September 5, 2023, 12:10pm UTC](https://discuss.rubyonrails.org/t/where-can-i-know-for-which-version-of-ruby-is-officially-tested-for-a-particular-version-of-rails/83647 "2023-09-05T12:10:57Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![tesssie](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/tesssie/32/10219_2.png) [@tesssie](https://discuss.rubyonrails.org/u/tesssie)\ **Post date:** [September 5, 2023, 12:10pm UTC](https://discuss.rubyonrails.org/t/where-can-i-know-for-which-version-of-ruby-is-officially-tested-for-a-particular-version-of-rails/83647/1 "2023-09-05T12:10:57Z")
I have a legacy application of ruby on rails 4.2 and ruby version 2.6. As ruby 2.6 upgrade has reached its end of life, I need to upgrade to ruby 3.1. when I checked [rails | RubyGems.org | your community gem host](https://rubygems.org/gems/rails/versions/4.2.11.3) its says only the lower limit. ie ruby version greater 1.9.3 is enough. It did not mention if its supported officially with ruby 3. but when I tried to rails 4.2 application on ruby 3. It failed . It failed even for ruby 2.7. So How can i know should I update my rails version or not? ---
**Author:** ![andy\_nutter-upham](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/andy_nutter-upham/32/1196_2.png) [@andy\_nutter-upham](https://discuss.rubyonrails.org/u/andy_nutter-upham)\ **Post date:** [September 5, 2023, 1:11pm UTC](https://discuss.rubyonrails.org/t/where-can-i-know-for-which-version-of-ruby-is-officially-tested-for-a-particular-version-of-rails/83647/2 "2023-09-05T13:11:16Z")
I always refer to this page: [Ruby & Rails Compatibility Table - FastRuby.io | Rails Upgrade Service](https://www.fastruby.io/blog/ruby/rails/versions/compatibility-table.html) ---
**Author:** ![claasz](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/claasz/32/5017_2.png) [@claasz](https://discuss.rubyonrails.org/u/claasz)\ **Post date:** [November 3, 2023, 2:57pm UTC](https://discuss.rubyonrails.org/t/where-can-i-know-for-which-version-of-ruby-is-officially-tested-for-a-particular-version-of-rails/83647/3 "2023-11-03T14:57:36Z")
> As ruby 2.6 upgrade has reached its end of life, I need to upgrade to ruby 3.1 Note that Rails 4.2 has reached end of life too. > It did not mention if its supported officially with ruby 3. For older Rails versions, you can look into [.travis.yml](https://github.com/rails/rails/blob/4-2-stable/.travis.yml) file to find out what Ruby versions it was tested with. Rails 4.2 was released on 2014-12-20, Ruby 3.0 on 2020-12-25. So when Rails 4.2 was released, nobody was aware of Ruby 3.0 - developers could only test against Ruby versions at that time. Of course somebody could take the effort and test compatibility of newer Ruby versions against old Rails versions, but I guess it’s not that interesting. My personal advice would be: If you have to maintain an old Rails app, stick to the Ruby version you know it’s running OK with. If you want to upgrade because of security concerns, you should upgrade the Ruby version _plus_ the Rails version _plus_ all the other versions from the Gemfile. ---
**Author:** ![railsup-sedin](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/railsup-sedin/32/12941_2.png) [@railsup-sedin](https://discuss.rubyonrails.org/u/railsup-sedin)\ **Post date:** [December 27, 2024, 10:20am UTC](https://discuss.rubyonrails.org/t/where-can-i-know-for-which-version-of-ruby-is-officially-tested-for-a-particular-version-of-rails/83647/4 "2024-12-27T10:20:03Z")
Rails 4.2 was released long before Ruby 2.7 and Ruby 3.0. These versions introduced breaking changes and deprecations. For ex, Ruby 2.7 and 3.0 introduced changes to how keyword arguments are handled, which Rails 4.2 doesn’t account for. Also, many of the gems you’re using might not support Ruby 2.7 or 3.0 when paired with Rails 4.2. You can also try using [RailsUp](https://www.railsup.io/). This is a free gems compatibility checker tool. You can analyze your app’s gemfile and identify outdated or incompatible gems. You can also get the complexity score and an estimate of the time required for the upgrade process. ---
**Author:** ![Lorin\_Thwaits](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/lorin_thwaits/32/9491_2.png) [@Lorin\_Thwaits](https://discuss.rubyonrails.org/u/Lorin_Thwaits)\ **Post date:** [December 29, 2024, 12:01pm UTC](https://discuss.rubyonrails.org/t/where-can-i-know-for-which-version-of-ruby-is-officially-tested-for-a-particular-version-of-rails/83647/5 "2024-12-29T12:01:02Z")
If you install **[The Brick](https://github.com/lorint/brick)** then a Rails 4.2 app will work with Ruby 2.7. And once there then you can upgrade your Rails versions all the way to 7.0. And once there you can upgrade your Ruby version to the latest, and finally upgrade all the way to Rails 8.0. ---
**Author:** ![walterdavis](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/walterdavis/32/705_2.png) [@walterdavis](https://discuss.rubyonrails.org/u/walterdavis)\ **Post date:** [December 29, 2024, 1:14pm UTC](https://discuss.rubyonrails.org/t/where-can-i-know-for-which-version-of-ruby-is-officially-tested-for-a-particular-version-of-rails/83647/6 "2024-12-29T13:14:39Z")
You’ve really made the Swiss Army knife here, haven’t you! Walter ---
**Author:** ![Lorin\_Thwaits](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/lorin_thwaits/32/9491_2.png) [@Lorin\_Thwaits](https://discuss.rubyonrails.org/u/Lorin_Thwaits)\ **Post date:** [December 29, 2024, 1:31pm UTC](https://discuss.rubyonrails.org/t/where-can-i-know-for-which-version-of-ruby-is-officially-tested-for-a-particular-version-of-rails/83647/7 "2024-12-29T13:31:35Z")
It’s pretty much a “Rails +” kind of option for either upgrading existing apps or creating new ones. (Or just quickly spinning up an admin panel to be used for development / testing.)