Rails 7.0 merge today

Hello,

For those following along with Rails 7 upgrade you can tell we’ve gotten close and today we feel that we’re ready. While you may still see some issues in nightly, at this point we’d like to roll forward. Otherwise we’ll have too little time until the holidays and if we miss that, we’re getting too late in the release cycle.

If you maintain a plugin that needs work, have a look a the various plugins that have already been updated. The official guide, Upgrade Rails From 6.1 to 7.0 - FastRuby.io | Rails Upgrade Service and Rails Upgrade: From 4.0 to 6.1 to 7.1 and Ruby 2.0 to 3.0 to 3.1.3 | by Ali Ahmad | Medium are what we used.

Rails 7.0 is a bit stricter in Zeitwerk than Rails 6.1 and explicit require statements are a red flag. Also changing the autoload paths is a bad sign. A great reference to start is:

Another common change is the deprecation of errors[:field] << my_error and instead you need to use errors.add(:field, my_error).

You may see broken nightly packages for a bit. If you do, please share it here or on Matrix.

9 Likes

After we merged it both the Foreman and Katello pipelines were green. Luna was red (Luna-nightly-rpm-pipeline 841 failed) but with a patched foreman_azure_rm hopefully it will turn green.

1 Like

It did, luna is now green Jenkins

While we may see more issues, I feel confident in calling it a successful upgrade and would like to give my special thanks to @ofedoren who did most of the preparations by submitting PRs.

4 Likes