Add missing migration snapshots and fix journal idx ordering#301
Merged
jakebromberg merged 1 commit intomainfrom Apr 5, 2026
Merged
Add missing migration snapshots and fix journal idx ordering#301jakebromberg merged 1 commit intomainfrom
jakebromberg merged 1 commit intomainfrom
Conversation
47d43a5 to
11ef133
Compare
Migrations 0032-0034 had SQL files and journal entries but no snapshot files, which would cause drizzle-kit generate to compute incorrect diffs. Added snapshots using the current schema state (0034) as the authoritative reference. Also fixed journal ordering: 0026_capabilities_column was appended after 0030 with a duplicate idx 27. Reordered all entries from idx 24+ by timestamp and assigned sequential idx values.
11ef133 to
5f6412f
Compare
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.
Summary
idx: 27in journal (0026_capabilities_column and 0027_cron_job_tracking both had idx 27)whentimestamp with sequential idx valuesCloses #296
Test plan
drizzle-kit generateno longer produces a spurious migrationnpm run drizzle:migrateagainst a fresh database to verify migration chain is intact