We’re now in the week before Foreman 3.13’s stabilization week (see Foreman 3.13 Schedule and Planning). While we’re not intending any further changes in 3.13, it does mean the 3.14 cycle is getting close. Overall we have a good feeling that we’re on track to merging Rails 7.0 early in the cycle.
The core PR now has some issues where it’s complaining about database access during webpack compilation. There we use nulldb which may be the cause.
On the dependencies we’ve released ldap_fluff 0.8.0 to include Allow activesupport 7.0 usage by ofedoren · Pull Request #85 · theforeman/ldap_fluff · GitHub. @aruzicka also noted we should verify scoped_search. In the time between the sync up and me writing this he already opened Try testing with active*-7.0.0 by adamruzicka · Pull Request #225 · wvanbergen/scoped_search · GitHub so we know it’s passing the test suite on targets we care about.
@ofedoren is still working on the plugins. Some PRs can already be merged because they’re Rails 6.1 compatible (like Fixes #37847 - Support Rails 7.0 by ofedoren · Pull Request #921 · theforeman/foreman_remote_execution · GitHub & Fixes #37850 - Support Rails 7.0 by ofedoren · Pull Request #190 · theforeman/foreman_templates · GitHub) while others can’t (Fixes #37846 - Support Rails 7.0 by ofedoren · Pull Request #762 · theforeman/foreman-tasks · GitHub). His current focus is on foreman_rh_cloud, katello and foreman_theme_satellite. Other plugin maintainers are still encouraged to look at their own plugin.