You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 319ebec
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: site/tests/release-cutover-runbook.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,6 +122,10 @@ This command verifies the retained manifest against its exact public release ass
122
122
123
123
If a failed site job is rerun, it downloads the npm evidence artifact named by the original completed release job, even when the workflow attempt number changes. If its delivery ref already selects this SHA, no new push or synthetic commit is made. Inspect or retry that exact Pages deployment through the authorized dashboard when appropriate; do not force a ref, move a version tag or republish npm to obtain a site retry. A new publication manifest with different bytes requires reconciliation, never `--clobber`.
124
124
125
+
Pages reconstructs the site from the same source and lockfile, then `hosted-verify` compares every output file with the immutable CI manifest before deployment. It does not directly upload the CI archive. After that comparison and the delivery-ref check succeed, `hosted-verify` atomically updates the build-local `wrangler.jsonc` with seven controlled plaintext build inputs: the actual Node version, repository-pinned Bun version, `SKIP_DEPENDENCY_INSTALL=1`, and the verified project, subdomain, portable-image and legacy-cutover values. This configuration is outside `site/out`; neither public output nor the CI manifest changes. Existing runtime variables, bindings and other configuration remain intact, and production variables keep Wrangler's non-inheritance semantics. Arbitrary process variables and dashboard secrets are never copied.
126
+
127
+
This synchronization is required on every Worker deployment: [Wrangler configuration is the Pages source of truth](https://developers.cloudflare.com/pages/functions/wrangler-configuration/), so an empty source `vars` map can replace dashboard plaintext build values. Verify the seven build inputs after delivery, including the actual channel's project and subdomain. Keep four explicit prefixes on each surface's Pages build command: `MASTER_CSS_PAGES_PROJECT`, `MASTER_CSS_PAGES_SUBDOMAIN`, `MASTER_CSS_IMAGE_TRANSFORMATIONS=false` and `MASTER_LEGACY_DESIGN_CUTOVER` aligned with its GitHub variable. Use that surface's real project/subdomain, including RC. Pages can apply source configuration before the hosted shell runs, so dashboard-only identity values are insufficient. A failed metadata, registry, output or delivery-ref check must leave the configuration untouched.
128
+
125
129
`release-artifacts/site-delivery.json` records the source, actual version, logical channel, delivery ref, project, mode and owning GitHub run/attempt before any asset/ref write. Each external write records its intent and acknowledged, rejected or unknown response outcome; asset/ref verification is recorded separately. A lost response can leave a successful remote write with an `unknown` outcome. A failed CLI status never means that no write occurred or that Cloudflare rolled back. Inspect the retained receipt and authoritative asset/ref state before retrying. Retries with an existing local receipt append an attempt without replacing its history; separate workflow attempts retain separate artifacts. Immutable-host and canonical verification flags become true only after their respective live checks complete. Failure receipts contain fixed phase/error codes, never raw responses, credentials or private dashboard identifiers.
126
130
127
131
1. Stage the exact verified output with its commit identity. A private preview and the new project's production `pages.dev` bootstrap are distinct deployment environments. Require the real `X-Robots-Tag: noindex` response on either Pages-hosted surface; do not assume a production bootstrap inherits preview defaults. The Git delivery watcher explicitly checks the immutable identity response header. Retain the immutable deployment URL because branch aliases can move. These Pages-host rules do not impose a separate JSON SEO requirement on the canonical domain. [Preview deployment documentation](https://developers.cloudflare.com/pages/configuration/preview-deployments/)
0 commit comments