Repository navigation
fix(db): make db-migrations CI green on cold replay - #37
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The year_label/subject_title drift warning predated the cold-replay repair that adds both columns in 20260623000003. Rewritten as resolved with the failure mode kept as a historical check.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backfills the rows that only ever existed as hand-made production data and that 006, 007, and the June 23 subject seed silently depend on:
…0001(1st Year) /…0002(2nd Year) — never seeded by any migration; June 23 seed FK-violates on year …000285eaf374…and World Literature045d09d8…— referenced by hardcoded UUID in 006/007 module INSERTs → FK violations on a fresh replayNew migration
005a_seed_missing_years_and_module_subjects.sqlis pureon conflict (id) do nothing, so it is a no-op against production. 006/007 stay byte-identical per the workflow's apply-unchanged contract.Plan + iteration log: docs/superpowers/plans/2026-08-25-db-migrations-green.md