fix(migrations): retimestamp scan tables after initial-schema.

Fresh CI/postgres runs failed because 1748365200000 sorted before
initial-schema. Renamed to 1779853647566 with IF NOT EXISTS guards intact.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Randall Stillwell 2026-06-02 08:49:10 -05:00
parent 37d38de7ff
commit 898d3973c0
2 changed files with 6 additions and 1 deletions

View file

@ -178,7 +178,7 @@
### card_submissions ### 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 | | Column | Type | Notes |
| --- | --- | --- | | --- | --- | --- |

View file

@ -1,6 +1,11 @@
/** /**
* card_submissions + scan_attempts for server-side scan pipeline. * 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} * @type {import('node-pg-migrate').ColumnDefinitions | undefined}
*/ */
export const shorthands = undefined; export const shorthands = undefined;