Deploy and roll back immutable releases

Build once, promote the same artifact

A BlinkHost production deployment points to an immutable artifact identity. Its release record includes source and build identity, artifact digest, release ID, and deployment state. Promotion does not rebuild source.

Verify production

After selecting Deploy, wait for Active. Compare the production response and operational release metadata with the deployment detail page. Keep the release ID and digest when investigating an incident.

Roll back

Open deployment history, select a prior healthy signed artifact, and choose Rollback Here. BlinkHost creates a new auditable rollback deployment that references that artifact. It does not rewrite history or rebuild the old commit.

If propagation fails, the previous healthy release should remain the recovery target. Use deployment logs and health evidence before attempting another change.