Promote a reviewed change

The common Git workflow merges an approved pull request into the production branch, triggering a new Production deployment.

Wait for the deployment to succeed before considering the release complete. Open the production domain, verify its deployment ID or commit, and perform the high-value smoke checks. Teams with explicit promotion settings can promote a tested deployment, but the same principle applies: know which immutable deployment receives production traffic.

Capture the previous production deployment before moving traffic. After the change, query the production domain and confirm it resolves to the intended deployment, not merely that the Preview URL still works. Test one static path, one dynamic path, one write, and the health signal while watching errors and latency.

Promotion moves code and built configuration; it does not reproduce Preview’s external data or undo a Production migration. Keep schema changes compatible with both old and new code during the rollback window. If a smoke check fails, use the recorded previous deployment to restore traffic, then reconcile the production branch before the next automatic release.

Merge the reviewed footer change, watch the Production deployment, and record the old and new deployment identifiers.