letsbe/pn-new-crm
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore(migrations): renumber 0020/0021 -> 0021/0022 to avoid clash with berth-parity

Browse Source 
berth-schema-parity branch already shipped its own migration 0020 (berth
schema parity: text -> numeric, +status_override_mode). Dedup's two
migrations need to land on top of that, not collide.

Renames:
  0020_unusual_azazel.sql       -> 0021_unusual_azazel.sql
  0021_magenta_madame_hydra.sql -> 0022_magenta_madame_hydra.sql
  meta/0020_snapshot.json       -> meta/0021_snapshot.json
  meta/0021_snapshot.json       -> meta/0022_snapshot.json

_journal.json idx + tag fields updated to match.

Snapshot CONTENTS remain dedup-branch state (no berths-numeric awareness).
A `pnpm drizzle-kit generate` after main merges the berth changes will
produce a consistent forward path; until then the snapshots are slightly
out-of-sync with the post-merge live schema, which is harmless because
the dev DB applies migrations forward, not from snapshots.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Ciaccio
2026-05-03 16:22:58 +02:00
parent 4bcc7f8be6
commit 7574c3b575
5 changed files with 29 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/lib/db/migrations/meta/_journal.json
View File

@@ -143,17 +143,17 @@
"breakpoints": true
},
{
"idx": 20,
"idx": 21,
"version": "7",
"when": 1777811835982,
"tag": "0020_unusual_azazel",
"tag": "0021_unusual_azazel",
"breakpoints": true
},
{
"idx": 21,
"idx": 22,
"version": "7",
"when": 1777812671833,
"tag": "0021_magenta_madame_hydra",
"tag": "0022_magenta_madame_hydra",
"breakpoints": true
}
]