Publish, promote and roll back

Publishing updates a distribution channel’s compatible-release catalog. It does not edit translations or merge branches. Only Owner/Admin can publish or roll back, and the workspace and project must be active. Existing delivery continues if they are archived.

Publish to Preview

Prepare and review a release.
Open Distributions, then select the application distribution.
Under Preview, choose the prepared release and select Publish to Preview.
Review the package, validation counts, compatibility range and resulting catalog.
Select Confirm publication. Track Release operations and both node acknowledgements.
Test only after the Preview operation is completed and both servers are Active.

Both nodes must durably verify all package files before the publication decision is committed. If a node is unavailable before that point, existing publications remain unchanged. After commit, the same recorded decision must finish; it cannot be cancelled.

The compatibility review counts removed keys, changed message formats/variable contracts and languages removed from overlapping publications. Open the comparison links to inspect the exact content. These checks identify risk; only testing your application establishes compatibility with its code.

Promote to Production

Use the distribution’s Preview key to test this exact release and its intended application versions.
Under Production, select the same release and Promote to Production.
Review the package again. There must be no unresolved translations in requested languages.
Explicitly confirm I tested this exact release and version range in this distribution’s Preview channel.
Select Confirm publication and wait for both server acknowledgements.

Promotion reuses the same immutable package. It does not rebuild from the branch. The test confirmation binds the release digest, compatibility bounds, distribution and successful Preview activation. A withdrawn or incomplete Preview publication cannot establish this prerequisite.

Application version selection

Each channel can contain several publications. For a supplied strict SemVer application version, delivery selects the latest activated, non-withdrawn publication whose inclusive bounds contain that version. Release numbers and package protocol versions are separate concepts. A SemVer prerelease suffix does not select Preview: the channel is explicit.

For example, a release targeting version 2.0.0 and later can coexist with an earlier publication for older applications. Overlapping ranges use activation order. Exact bounds are never inferred from ambiguous strings such as v2, latest or 2.x.

Review and apply a rollback

In the channel’s Publication history, find the publication to withdraw.
Select Review rollback. Review Affected application versions, including inclusive/exclusive endpoints, and the replacement release for each affected interval.
Select Confirm rollback and wait for both nodes.

Only the selected publication is withdrawn. Each affected version resolves to its latest compatible remaining publication. If any affected version would have no replacement, rollback is blocked; publish a corrected release instead. The first publication cannot be rolled back without compatible replacement coverage.

Rollback creates a new increasing channel revision. A delayed older manifest must not undo that decision. Withdrawn packages and audit records remain stored. Publications in other channels or distributions are unaffected. Offline clients learn the change on their next successful update; already downloaded bytes are not remotely erased.

Conflicts and partial activation

A review expires after 24 hours and is tied to the channel revision. Another publication or rollback makes it stale: discard it and review again. A channel with unresolved activation rejects another publication.

Partially active means one node has acknowledged the committed decision and the other has not. It does not mean both have switched. Restore the unavailable node and use Retry operation. Retries finish the same decision and do not create another publication or revision. Keep the saved decision when restoring from backup.

Optional translation review requirement

Project settings can require review evidence for the exact direct or fallback revisions used by each new Production publication. Preview stays available; approving unchanged text after Preview can qualify the same package. Existing publications and rollback remain unchanged. See Production review policy.