Description of problem: On table recipe_activity recipe_id is nullable which can lead to orphaned data. This should be made nullable=False. In the migration script need to delete the potential orphans when making this change.
On a recent production snapshot: MySQL [beaker_dcallagh]> select count(*) from recipe_activity where recipe_id is null; +----------+ | count(*) | +----------+ | 0 | +----------+ 1 row in set (0.00 sec)
https://gerrit.beaker-project.org/5959
There is no expected change in behaviour here, so verification should just be that the database migration succeeds (it did) and that nothing else breaks.
Beaker 25.0 has been released. Release notes are available upstream: https://beaker-project.org/docs/whats-new/release-25.html