Browse documentation
Publishing
Build immutable releases, promote production safely, and recover with rollback.
On this page
Release process
Publishing snapshots the required site inputs and queues a release build. The worker compiles pages and runtime assets, verifies artifact integrity, and records the completed release without mutating production.
Promotion is a separate action. Production changes only after the release is complete, authorized, and compatible with the current site state.
- 01
Check readiness
Resolve missing routes, invalid bindings, domain blockers, and required approvals.
- 02
Build the release
Create immutable page and runtime artifacts from pinned inputs.
- 03
Inspect staging
Verify navigation, forms, responsive behavior, metadata, and critical interactions.
- 04
Promote production
Point the production environment at the completed release.
Rollback
Rollback promotes a previously completed compatible release. It does not rebuild the old site from current documents.
Use rollback to restore service quickly, then diagnose the failed release separately. Confirm that external dependencies and data assumptions remain compatible with the selected release.
Rollback is not content undo
Rolling production back does not change the current editor document or erase newer work. Use document history when you need to restore editable source.
Still need help?
Find recovery guidance or contact the DevAssistant team.