ci: retire the Cloudflare Pages pull_request shadow trigger (production lane keeps push:main) - #248
ci: retire the Cloudflare Pages pull_request shadow trigger (production lane keeps push:main)#248Jesssullivan wants to merge 1 commit into
Conversation
…ne is production The pull_request trigger produced build-only runs with can_deploy=false that read as green 'shadow' checks on every PR, while real PR iteration moved to the tailnet shadow route (shadow-preview.yml). push:main + workflow_dispatch remain: they are the transscendsurvival.org production deploy. Filename kept (BUILD.bazel + contract tests reference it); workflow/job names now say production.
GitHub Actions
Error
|
TIN-2801 remains an unresolved prod-blocker. The PR-triggered shadow receiver run 31640582730 and source run 31640031567 were cancelled before apply, and this PR is returned to draft to prevent another automatic receiver dispatch. The broader TIN-603/TIN-604 replacement will preserve exact-SHA provenance and make both shadow apply and production publication fail closed behind explicit operator gates. Branch retained; no merge or deploy authorization is implied. |
|
Scope +1 commit: the shadow-preview |
1 participant
Hygiene-week item (operator-ratified: pages PR-shadow deprecated as CI/CD).
pull_requesttrigger block and the PR-skip/GITHUB_HEAD_REFlogic — those runs never deployed (can_deploy=false) and produced misleading green "shadow" checks on every PR.push:main+workflow_dispatch: that path IS the Cloudflare Pages production deploy for transscendsurvival.org, and is renamed accordingly (workflow/job/summary strings).BUILD.bazeland contract tests reference it; an in-file comment now records the role.shadow-preview.yml(unaffected).build-and-test/substrate-boundary/bazel-remote-gatesare), so removal can't wedge merges.