Migration 73 is missing #15306
Description
What is this about?
In a previous commit, migration 73 was removed entirely. However, while 73 existed, more migrations were added. As a result there is now a "hole" in the list of migrations, and the number of migrations does not match the number of the latest migration. We've never done this before, and there is code in the migration which assumes that no holes are present. As a result it's possible that if a user is at migration 72, migration 74 will be skipped (because the runner may think this is 73). We should add 73 back but as a dummy migration.
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
- Engineering (needed in most cases)
- Design
- Product
- QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- Security
- Legal
- Marketing
- Management (please specify)
- Other (please specify)
References
No response