ci: run migrations against Postgres service container in CI #64
2 changed files with 6 additions and 1 deletions
|
|
@ -178,7 +178,7 @@
|
|||
|
||||
### card_submissions
|
||||
|
||||
Added by `migrations/1748365200000_add-scan-tables.js` (server-side scan pipeline). Unknown high-confidence scans queue here for admin review instead of polluting `cards`.
|
||||
Added by `migrations/1779853647566_add-scan-tables.js` (server-side scan pipeline). Unknown high-confidence scans queue here for admin review instead of polluting `cards`.
|
||||
|
||||
| Column | Type | Notes |
|
||||
| --- | --- | --- |
|
||||
|
|
|
|||
|
|
@ -1,6 +1,11 @@
|
|||
/**
|
||||
* card_submissions + scan_attempts for server-side scan pipeline.
|
||||
*
|
||||
* Retimestamped from 1748365200000 → 1779853647566 so fresh DBs run
|
||||
* initial-schema before scan tables (FK to users). Existing envs that
|
||||
* already recorded the old name in pgmigrations are unaffected; IF NOT EXISTS
|
||||
* guards make re-application safe if the new name is pending.
|
||||
*
|
||||
* @type {import('node-pg-migrate').ColumnDefinitions | undefined}
|
||||
*/
|
||||
export const shorthands = undefined;
|
||||
Loading…
Reference in a new issue