fix(db): keep check:pg-baseline speaking once the baseline is frozen

A frozen baseline still has its manifest verified, and the check now lists the
migrations that run on Postgres after the cut and what holds them. Every
problem it reports says what to do about it.
This commit is contained in:
Maurice
2026-11-17 11:48:18 +01:00
parent a748d6c554
commit 53d875aecb
3 changed files with 95 additions and 26 deletions
+4 -3
View File
@@ -284,11 +284,12 @@ jobs:
# migration that changes a column regenerates it in the same change.
run: cd server && npm run check:db-types
- name: Postgres baseline matches the entities
- name: Postgres baseline manifest (and entities until a migration follows the cut)
# server/assets/postgres/ is the schema a fresh Postgres database starts
# from, generated from the entities by gen:pg-baseline. Until a migration
# lands after its cut it must match them exactly; after, it is frozen
# and only its list of migrations is checked.
# lands after its cut it must match them exactly; after, it is frozen,
# its list of migrations is checked and the migrations after the cut are
# listed: lint:dialect holds their engineDdl and PARITY-PG their result.
run: cd server && npm run check:pg-baseline
server-lint-checks: