fix: migration 033 idempotency & smoke test cleanup (#365)

* fix(core): add IF NOT EXISTS to migration 033 index creation

The schema registry's createContentTable() creates composite indexes
on content tables at creation time. When migration 033 runs on a
database where tables were created after the registry added these
indexes, it fails with "index already exists". Adding IF NOT EXISTS
makes the migration idempotent.

* refactor(smoke): trim site matrix to templates + playground, remove typechecks

The smoke test matrix included every demo and template, plus typecheck
cases. This was slow and redundant — typechecks are already covered by
pnpm typecheck, and demos are dev targets not release artifacts.

Trim to templates + playground only, and replace the sequential per-site
astro build with a single recursive pnpm build. Remove the TypecheckSiteCase
type and handling since smoke tests should only verify runtime behavior.

* Update env

* chore: add changeset for migration 033 fix
This commit is contained in:
Matt Kane
2026-04-07 23:00:54 +01:00
committed by GitHub
parent f112ac4819
commit d6cfc437f2
6 changed files with 25 additions and 128 deletions

View File

@@ -0,0 +1,5 @@
---
"emdash": patch
---
Fixes migration 033 failing with "index already exists" on databases where the schema registry had already created composite indexes on content tables.