Use local Forgejo runner label
Some checks failed
ci-gates / checks (push) Failing after 1s
deploy-cloudflare / checks (push) Failing after 1s
deploy-cloudflare / deploy (push) Has been skipped

This commit is contained in:
Conrad Kramer 2026-06-10 03:19:02 -07:00
parent b49dcff27d
commit 81724b7030
No known key found for this signature in database
5 changed files with 9 additions and 7 deletions

View file

@ -47,5 +47,7 @@ status, and first observable canvas frame when the browser exposes it.
Ship the static web change with the existing Worker asset deploy and roll the publisher hotpatch
binary to the LA nodes so their catalogs match the current watcher schema. Validate with clean-cache
desktop/mobile browser loads and check the app's `window.__ecPerf` marks plus a live tune through the
public relay. Teardown is removing the HTML seed/cache/warmup path, returning to live-API-only station
rendering, and explicitly passing `--passthrough=false` only if an older watcher path is restored.
public relay. The Forgejo workflows use the locally registered `namespace-profile-linux-medium`
runner label so the Cloudflare deploy can actually leave the queue on the self-hosted forge.
Teardown is removing the HTML seed/cache/warmup path, returning to live-API-only station rendering,
and explicitly passing `--passthrough=false` only if an older watcher path is restored.