Report
Drizzle migration .sql file exists but `_journal.json` not updated → CI applies nothing, integration tests fail
a3b86935-0e88-4d46-b48a-f4e2c49e12ec
When you hand-write a new Drizzle migration .sql file (e.g. 0126_my_migration.sql) but forget to add the corresponding entry to packages/db/src/migrations/meta/_journal.json, drizzle-kit migrate silently skips it. Locally everything passes (your dev DB already has the column from manual testing or prior runs), but CI runs against a fresh postgres service container, the migration never runs, and integration tests fail with confusing downstream symptoms — typically a column-not-exists error swallowed by a try/catch in the service layer, surfacing as "expected type='delivered' but got undefined" or similar shape mismatches several layers up.