ci: keep Pages publish on the trusted alkane-verify runner
source / check (pull_request) Skipped
verify / verify (pull_request) Successful in 14m59s
verify / verify-windows (pull_request) Skipped

The check-runner-image.py guard (run inside the verify gate) requires
pages.yml publish to stay on alkane-verify (the trusted verifier) and
forbids publishing Pages from the GARM pool. The blanket repoint moved
it to alkane-ci, which failed the gate:
  "Pages must follow main CI on the trusted verifier".

Revert only pages.yml to alkane-verify; verify/source/bench-pages/
ci-badge stay on alkane-ci. Pages publishing waits on alkane-verify
being restored, but that job is workflow_run-triggered off main and is
not a PR gate, so PR verification is unblocked.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B1W6qKwKxq3oUPDKWicM6i
This commit is contained in:
2026-11-16 15:49:59 -06:00
co-authored by Claude Opus 4.8
parent ed8ef96e64
commit b0dee03f0f
+1 -1
View File
@@ -17,7 +17,7 @@ concurrency:
jobs:
publish:
runs-on: alkane-ci
runs-on: alkane-verify
container:
image: gitea.bluefla.re/blueflare/alkane-ci@sha256:4929b2979851f1f12fb8f92ef74236ae4c2ea735a41ead94a16af416a4f0a1a5
permissions: