v0.56.4 — Hotfix: the alpha deploy gate refused its own green commits
The alpha deploy workflow's stability gate counted every failing check run on the
tagged commit, which made it poison its own input. When alpha's resolve job fails,
GitHub records a failing check run against that commit; once a tag pointed there, every
later run saw that failure and refused to deploy — permanently, with no remedy but
deleting the tag. Non-gating checks (CodeQL, the terraform linter) had the same effect.
The gate now considers only the CI jobs that actually gate a release, lint-and-test and
migration-guard. Verified against the live check-runs API: df60779e (v0.56.3 — green
CI, but carrying a failed resolve from the blocked run) reports 0 failing gating checks
and deploys, while c95707b0, whose lint-and-test genuinely failed, still reports 1 and
is still refused.
This also restores tag/deploy parity. Prod deploys on pushes to main, but alpha selects
the newest vX.Y.Z tag — and v0.56.2 and v0.56.3 shipped to prod without ever being
tagged. Alpha therefore kept resolving to v0.56.1, a tag that points at the
"v0.56.2 - module bump" commit and whose lint-and-test had failed. package.json had
likewise stayed at 0.56.1 through both releases.
- Alpha's stability gate counts only
lint-and-testandmigration-guard - Tagged v0.56.4 so alpha and prod agree on the latest release
package.jsonmoved to 0.56.4, catching up the two untagged hotfixes