From 9530e5d3c78050da5faba7b9e19395808bf30b2f Mon Sep 17 00:00:00 2001 From: macanderson Date: Thu, 23 Jul 2026 23:27:50 -0700 Subject: [PATCH] ci(site): promote docs-site build from advisory to a hard gate The site job carried continue-on-error: true, so a broken marketing surface could ship silently. The advisory comment said to flip it to a hard gate once the build had been stable for a release cycle; that has held, so remove continue-on-error and make the docs-site build a required check. Verified locally: pnpm install --frozen-lockfile + next build both pass (Next 16, 16/16 static pages), so the gate is green on flip. --- .github/workflows/ci.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index b6b22be..8ec05f7 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -150,10 +150,10 @@ jobs: site: name: docs site builds runs-on: ubuntu-latest - # Advisory: the site is a marketing surface, not a normative artifact, and - # a broken lockfile there must not block a spec change. Flip to a hard gate - # once the site build has been stable for a release cycle. - continue-on-error: true + # Hard gate: the docs site build must pass. It was advisory-only + # (continue-on-error) during early churn so a broken lockfile there could + # not block a spec change; now that the build is stable it is promoted to a + # required check, so a broken marketing surface can no longer ship silently. steps: - uses: actions/checkout@v5 - uses: pnpm/action-setup@v4