Understand the release boundary
Draft edits are private. A release freezes the document, route claims, required media derivatives and dependent CMS content needed by that version.
A later draft edit cannot silently change an existing release. Commerce stays dynamic only at reviewed server boundaries where Tebex is authoritative.
Run preflight and approval
- Save the latest revision and resolve optimistic-write conflicts.
- Run publish diagnostics for schema, routes, localized SEO, media, links and component accessibility.
- Inspect the immutable preview and release diff.
- Collect the configured one-to-three approvals without allowing the author to satisfy prohibited self-approval rules.
Promote and rollback
Promote the approved release to staging or production. A scheduled promotion is generation-fenced so cancel, replacement and retry cannot publish an obsolete target.
- Verify public navigation, localized routes, one catalogue page and checkout hand-off after promotion.
- Rollback selects a prior immutable release; it does not mutate either version.
- Treat cache purge or domain health failure as a rollout incident and keep the last known good release serving.