lonsun
commented
8 years ago Upgraded to ruby 2.1.8 and rails 4.1.8. The latter was necessary to overcome some dependency issues.
Closed lonsun closed 8 years ago
lonsun
commented
8 years ago Upgraded to ruby 2.1.8 and rails 4.1.8. The latter was necessary to overcome some dependency issues.
Hello,
On Feb 24, 2016, Ruby 2.0.0 security maintenance will reach its end-of-life. When this happens, Ruby 2.0.0 will no longer receive security updates. We recommend that you upgrade your app to a supported Ruby version, e.g. 2.2.4, to ensure that your application is running in a secure environment.
After Feb 24, 2017, a year from the Ruby 2.0.0 sunset date, you will no longer be able to push your application using the official buildpack without upgrading to a supported Ruby version.
The following apps which have received traffic recently, that you own or are collaborated on, currently run on Ruby 2.0.0:
To migrate your app, you will need to add ruby "2.2.4" line to the top of your Gemfile if it doesn't already exist.
From there, you can do a normal deploy:
$ git add Gemfile $ git commit -m "Upgrading Ruby to 2.2.4" $ git push heroku master For more details on updating your Gemfile to specify a supported Ruby see this Dev Center article.
One thing to note when upgrading your Ruby 2.0.0 app, is that Ruby is known to use slightly more memory for increased performance. If you run into R14 errors because of this, please take a look at this article
On the sunset date, Heroku will release a legacy version of its buildpack that will continue to run Ruby 2.0.0, but it will be unsupported. Please see refer to our Language Sunset Policy for more information.
We encourage you to do upgrade as soon as possible. If you have any questions, please let us know.
Happy coding,
Heroku