Ruby Versions and Cedar 14
Last updated 15 November 2017
This article is a work in progress, or documents a feature that is not yet released to all users. This article is unlisted. Only those with the link can access it.
The Cedar-14 stack does not support certain versions of Ruby 2.1. If you deploy your app and get an error stating that your Ruby could not be installed, then you might need to use a more recent version of Ruby.
See the list of supported Ruby versions.
How to update
Specifying a version of Ruby can be done by updating your Gemfile.
For example, if your Gemfile has this line:
Please update it to a more recent Ruby version in the
2.1 family, for example
You can find the latest supported version of Ruby 2.1 on the Ruby support page.
Prior to Ruby 2.1, the Ruby project used version scheme that included
<major>.<minor>.<teeny>-<patch> such as
1.9.3-p545. As security releases came out, the patch would change, but the rest of the version
1.9.3 would stay the same. This is no longer true.
Now Ruby no longer uses a patch version and updates the
<teeny> on security fixes. This means that
2.1.4 should be identical to
2.1.0 except that it has performance and security fixes. You should always be using the latest patch level of a Ruby version available.
It is important to note that while this looks like semver, it is not. Ruby will from time to time release backwards incompatible patches for security vulnerabilities that cannot be fixed otherwise.