ci: validate main after merge and check migrations #100

Sammanfogat

supernaut sammanfogade 1 incheckning från ci/validate-main in i main

2026-07-29 18:49:17 +00:00

supernaut kommenterad

2026-07-29 18:02:54 +00:00

Ägare

CI was pull_request-only, so nothing validated main after a merge (#55).

A squash or rebase merge produces a commit that no pull_request run ever saw, so breakage that
exists only on the merged result went uncaught. Worse, once branch protection requires the ci
check, a base branch quietly failing its own CI blocks every later PR — which is exactly what
happened in bitborg-reconcile-trigger, where main sat with a README.md that failed
format:check and the symptom surfaced as an unrelated Renovate PR failing.

All five repos shared this gap; this is one of the five matching PRs.

Scoped to main, so it does not double-run CI: pushes to PR branches still only fire
pull_request.

Also: migration check

Added pnpm drizzle-kit check (#57) — migration-journal integrity plus branch-collision
("commutativity") detection, which catches a generated migration that no longer matches the schema,
or two branches that each added a migration and would collide on merge.

No database, no network — it reads drizzle/meta/ only. Verified green before wiring it in:
Everything's fine.

Refs #55, #57

CI was `pull_request`-only, so nothing validated `main` after a merge (#55). A squash or rebase merge produces a commit that no `pull_request` run ever saw, so breakage that exists only on the merged result went uncaught. Worse, once branch protection requires the `ci` check, a base branch quietly failing its own CI blocks **every** later PR — which is exactly what happened in `bitborg-reconcile-trigger`, where `main` sat with a `README.md` that failed `format:check` and the symptom surfaced as an unrelated Renovate PR failing. All five repos shared this gap; this is one of the five matching PRs. Scoped to `main`, so it does not double-run CI: pushes to PR branches still only fire `pull_request`. ## Also: migration check Added `pnpm drizzle-kit check` (#57) — migration-journal integrity plus branch-collision ("commutativity") detection, which catches a generated migration that no longer matches the schema, or two branches that each added a migration and would collide on merge. No database, no network — it reads `drizzle/meta/` only. Verified green before wiring it in: `Everything's fine`. Refs #55, #57

supernaut lade till 1 incheckning

2026-07-29 18:02:54 +00:00

ci: validate main after merge and check migrations

ci / ci (pull_request) Successful in 57s

Detaljer

87503f7759