Detect migrations dated in the future
A migration dated in the future (2026
) was introduced on !60720 (merged) which caused a production incident gitlab-com/gl-infra/production#4569 (closed). Manually checking for timestamps is something that can be easily missed during review, we should aim to automate this task.
Proposal
Introduce a CI job that fails if migration files are dated in the future (e.g next year).
To do
-
Implement the CI job !61473 (merged) -
Test that it's working !61473 (comment 576004937)
Edited by Mayra Cabrera