As part of the v2.29.0 release, a database migration fork was introduced due to PR #1446 and PR #1401 both adding migration scripts but pointing to the same past revision. I believe the reason is because the unit tests don't test the database migration scripts or the tests were both run before the other PR was merged.
Either way, perhaps the best approach is to have the C3I postmerge tests test the database migration scripts. Other ideas are welcome.
to comment on this ticket.