Release primary Worker candidate through dedicated workflow

This commit is contained in:
Kevin
2026-09-02 02:07:50 -04:00
parent 2a37841044
commit c48c9d4094
2 changed files with 7 additions and 2 deletions
@@ -1,6 +1,9 @@
name: Deploy primary production Worker candidate name: Deploy primary production Worker candidate
on: on:
push:
branches: [astro-platform-pilot]
paths: [.gitea/workflows/production-candidate.yml]
workflow_dispatch: workflow_dispatch:
jobs: jobs:
+4 -2
View File
@@ -20,8 +20,10 @@ static assets to a distinct Worker.
- Existing Pages production deployment: `2fb1b659-5928-4470-bb04-ef4c9105b843` - Existing Pages production deployment: `2fb1b659-5928-4470-bb04-ef4c9105b843`
from the `main` branch. from the `main` branch.
- Preview Worker: `3031023-xyz-www-preview`, with no custom domains or routes. - Preview Worker: `3031023-xyz-www-preview`, with no custom domains or routes.
- Production candidate Worker: `3031023-xyz`, deployed only through the manual - Production candidate Worker: `3031023-xyz`, deployed only through the
`Deploy primary production Worker candidate` workflow. dedicated `Deploy primary production Worker candidate` workflow. Its push
trigger is limited to changes to that workflow file; ordinary site commits
cannot update this Worker.
## Cutover sequence (requires separate approval) ## Cutover sequence (requires separate approval)