refactor(db): squash migrations into a single baseline #91

Merged
developer merged 1 commits from feature/squash-migrations into development 2026-06-20 13:23:44 +00:00
Owner

What

Squash the incremental goose migrations (0000100014) into a single 00001_baseline.sql. Migrations-only change — no schema or behaviour change.

How it was built / verified

  • Generated from the end-state schema of the full 0000100014 set (pg_dump), wrapped in goose.
  • Verified schema-identical: applied the single baseline to a fresh DB and pg_dump-diffed against the old set → identical.
  • The default house ad-campaign seed (the only data in the old migrations, in 00006) is carried over by hand (a schema-only dump omits it).
  • Full integration suite green against the single baseline.
  • Per-feature narrative is preserved in git history + docs/ARCHITECTURE.md.

Deploy note (the "drop db")

This breaks goose's version continuity (the contour DB is at v14; the baseline is v1). After merge the test contour DB must be wiped once — DROP SCHEMA backend CASCADE + restart scrabble-backend — so goose re-applies the single baseline fresh. No production data exists. I'll do this once the deploy lands.

## What Squash the incremental goose migrations (`00001`–`00014`) into a single `00001_baseline.sql`. Migrations-only change — no schema or behaviour change. ## How it was built / verified - Generated from the **end-state schema** of the full `00001`–`00014` set (pg_dump), wrapped in goose. - **Verified schema-identical**: applied the single baseline to a fresh DB and `pg_dump`-diffed against the old set → identical. - The default house **ad-campaign seed** (the only data in the old migrations, in `00006`) is carried over by hand (a schema-only dump omits it). - **Full integration suite green** against the single baseline. - Per-feature narrative is preserved in git history + `docs/ARCHITECTURE.md`. ## Deploy note (the "drop db") This breaks goose's version continuity (the contour DB is at v14; the baseline is v1). After merge the test contour DB must be wiped once — `DROP SCHEMA backend CASCADE` + restart `scrabble-backend` — so goose re-applies the single baseline fresh. No production data exists. I'll do this once the deploy lands.
developer added 1 commit 2026-06-20 13:11:54 +00:00
refactor(db): squash migrations into a single baseline
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 10s
CI / integration (pull_request) Successful in 15s
CI / ui (pull_request) Has been skipped
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Successful in 1m9s
483e945209
Consolidate the incremental goose migrations (00001-00014) into one
baseline. There is no production data, so the squash carries no data
migration. The baseline was generated from the end-state schema and
verified schema-identical to the squashed set (pg_dump diff) plus a full
integration run; the default house ad-campaign seed is carried over (a
schema-only dump omits it). The per-feature narrative that lived in the
squashed migrations is preserved in git history and docs/ARCHITECTURE.md.

Deploy note: this breaks goose's version continuity, so the test contour
DB must be wiped once — DROP SCHEMA backend CASCADE + restart backend —
for goose to re-apply the single baseline fresh. No prod data exists.
owner approved these changes 2026-06-20 13:23:31 +00:00
developer merged commit c739f12d3d into development 2026-06-20 13:23:44 +00:00
developer deleted branch feature/squash-migrations 2026-06-20 13:23:44 +00:00
Sign in to join this conversation.
No Reviewers
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: developer/scrabble-game#91