Enforce `Migration[2.0]` to make all migrations decomposition supported
What does this MR do and why?
The Migration[2.0]
was introduced around 25th of April. Since that time all migrations
do use [2.0]
and all outstanding and known bugs described in Rollout of `Gitlab::Database::Migration[2.0]` w... (#358430 - closed)
are fixed, including support for background and batched migrations and ability to finalize those.
There appears to be no known problems. This makes the Migration[2.0]
since that date
mandatory and an only supported way. That date is being picked to ensure that old MRs
that might have not updated timestamp of migrations will notice this requirement.
This is meant to avoid merging very old migration that would slip through a mechanism
how we enforce migration version: timestamp validation.
This also reverts a change introduced by !87412 (merged) since the outstanding problem was resolved.
Closes: Rollout of `Gitlab::Database::Migration[2.0]` w... (#358430 - closed) Enforce usage of `Gitlab::Database::Migration[2... (#358435 - closed)
Related:
- Enforce usage of `Gitlab::Database::Migration[2... (#358435 - closed)
- Rollout of `Gitlab::Database::Migration[2.0]` w... (#358430 - closed)
- Depends: !88493 (merged)
This requires the !88493 (merged) to be merged first.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.