| status | implementation | status_last_reviewed | status_notes |
|---|---|---|---|
superseded |
superseded |
2024-03-06 |
GOV.UK has a policy on keeping software current: https://docs.publishing.service.gov.uk/manual/keeping-software-current.html |
One of our core values is to use secure and up to date software. This document lays out the recommendations for keeping our Ruby on Rails software current.
We run a lot of Rails applications. This means that we have dependencies on both Rails and Ruby versions.
It's very important that we're running a currently supported version of Rails for all applications, otherwise we aren't covered by security fixes. We should:
- Be running on the current major version - this currently means
4.y.z - Maintain our applications at the latest current bugfix release for the minor version we're on (expressed in Gemfile syntax as:
~> X.Y.Z) - this currently means4.1.8and4.2.3 - Keep abreast of breaking changes for the next major version (
5.y.z), and have a plan to migrate our apps before4.2.xis deprecated
New versions of Ruby bring us improved performance and nicer syntax for certain things, but also can cause issues with the libraries etc. we use. We should:
- Be running on the current major version - this currently means
2.y.z - Maintain our applications at the current or next-to-current minor version - this means
2.2.zor2.1.z, depending on your app's dependencies
The current state of the Ruby and Rails versions is:
- Listed in this versions spreadsheet by alext
- Another spreadsheet with team ownership by alexandria.jackson.