ci: run migrations against Postgres service container in CI #64
No reviewers
Labels
No labels
agent-context-drift
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rstillwell/deckhearth#64
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/wire-migrate-into-ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
migrateCI job that runsnpm run migrate upagainst an ephemeral Postgres 16 service container on every PR/push tomain.POSTGRES_URLinto.env.localat job time sonode-pg-migrate's--envPath .env.localworks without Neon secrets or a committed env file.pg_isready) and targetsdeckhearth_teston localhost:5432.Test plan
migratejob passes on this PR (Postgres 16 service +npm run migrate up).pg_trgmmigration (1779853647565_add-pg-trgm-card-name-index.js) applies on the service container.Notes
POSTGRES_URL=postgres://postgres:postgres@localhost:5433/deckhearth_test npx node-pg-migrate ... upagainstpostgres:16reaches migrations;1748365200000_add-scan-tablesruns before1779853647564_initial-schemaand fails on a fresh DB (relation "users" does not exist). Existing envs that ransetup-neon-db.jsfirst are unaffected. If the migrate job fails in CI, a follow-up to re-timestamp or merge scan tables into initial-schema is likely needed.npm run test:runlocally: 52/53 pass; one pre-existing failure inScannedCardItem.test.js(ownershiprole=statusassertion) unrelated to this change.Made with Cursor
The latest updates on your projects. Learn more about Vercel for GitHub.
Pipeline Health
Build + CI gates
Build runs on Vercel; this CI runs lint and schema-map drift only (no duplicate build).
Role reports
See individual comments above for details. This rollup updates automatically.