Build once, promote the tested candidate
Do not rebuild after staging approval. If source, dependencies, configuration, generated assets, or output changes, repeat the complete gate.
Astro production checklist
A production release checklist that can say no.
A release process matters most when it stops an incomplete candidate. The Go for Launch checklist defines required evidence, promotion order, and explicit stop conditions.
What the process produces
- Lockfile install and diagnostics
- Built-candidate browser suite
- Native iOS Safari record
- Staging identity check
- Eight PageSpeed scores of 100
- Post-release canonical smoke test
Record evidence, not confidence
Preserve the candidate identifier, source revision, test results, Simulator environment, PageSpeed scores, deployment ID, public-host checks, and remaining risks.
Stop cleanly when a gate fails
Block production on diagnostics, browser behavior, native Safari, route completeness, forms, overflow, staging identity, or any PageSpeed score below 100. Fix and retest rather than waiving the result.