Only latest version of rails in the 5.x main release gets security updates, so once we have upgraded from 5.0 to 5.1, we cannot stop; we have upgrade to the latest in the the 5.2 main release. At this moment in time that's 5.2.7.1
What to do:
- [DONE] upgrade Rails and dependent gems with once that still support ruby 2.4
- [DONE] secret_key_base change https://github.com/rails/rails/pull/30067 and https://stackoverflow.com/q/51466887/520567
- [DONE] go through upgrade guide points 1 and 2
- [DONE] anothere set of upgrade notes
- [DONE] go through notable changes in release notes
- [DONE] remove workarounds and monkey patches in code pointed to by `rg -i "rails.*5\.2"`
- [DONE] formtastic update or fix errors (jgallaso)
- [DONE] regenerate database schema as Rails 5.2 updated format
- [DONE] upgrade all hashes to SHA256 (see
THREESCALE-5725)
The list in THREESCALE-8607 can be done after the upgrade.
- blocks
-
THREESCALE-5725 Make porta compatible with FIPS-enabled Openshift
-
- Closed
-
-
-
- Closed
-
-
THREESCALE-8354 Ditch Webpacker in favor of Shakapacker
-
- Closed
-
-
THREESCALE-2924 Bubble up errors from children of Proxy on Proxy updates (ui + API)
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is related to
-
THREESCALE-4950 After upgrading to 2.8 errors are found in system-provider
-
- Closed
-
-
-
- To Develop
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- To Develop
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- mentioned on
