Files
open-design/.github
lefarcenandGitHub d5aeab77fc fix(ci): push the release-cut baked manifest as a ruleset bypass bot (#5358)
* fix(ci): push the release-cut baked manifest as a ruleset bypass bot

bake-plugin-previews-release.yml renders every preview on a release/** cut and
pushes the authoritative manifest straight onto the release branch. But release/**
is guarded by the 'Protected branches (preview/*, release/v*)' ruleset whose
pull_request rule rejects direct pushes — and the workflow pushed with
PREVIEW_BAKE_TOKEN||github.token, i.e. github-actions[bot], which is NOT a bypass
actor. So the writeback failed with 'GH013: Repository rule violations found for
refs/heads/release/vX.Y.Z' (observed on release/v0.14.2), and the release branch's
bundled data/plugin-previews/manifest.json was never refreshed — the packaged app
then falls back to rendering each preview as a live iframe (pathological for the
WebGL example templates).

Mint an open-design-bot token (app id 3640364 — already a bypass actor on that
ruleset, same App the metrics/blog/contributors workflows use) after the render
and push with it via an explicit token URL. persist-credentials: false on checkout
so the leftover github.token extraheader can't override the inline bot token on
push (same failure mode fixed in #5357). No ruleset change required — the bypass
actor already exists; the workflow just wasn't using it.

* test(ci): lock the release-cut bake's ruleset-bypass push contract

Per .github/AGENTS.md, cross-workflow auth changes must update topology coverage
in e2e/tests/packaged-smoke-workflow.test.ts rather than rely on YAML review.
Add a companion assertion (alongside the existing bake-plugin-previews.yml one)
that locks bake-plugin-previews-release.yml's three co-dependent auth invariants:
persist-credentials: false on checkout, the open-design-bot token mint
(BOT_APP_CLIENT_ID/BOT_APP_PRIVATE_KEY — the App that is a ruleset bypass actor,
not RELEASE_BOT_APP_ID), and the explicit x-access-token:${BOT_TOKEN} push. A
refactor dropping any one silently reintroduces the GH013 rejection that stranded
release/v0.14.2's manifest.
2026-07-09 11:10:06 +00:00
..
2026-06-19 03:22:43 +00:00