Skip to main content
The remote working definition is editable state. A portal version is an immutable snapshot that can be activated. Activation changes what end users receive.

Complete the working definition

Use this release sequence:
  1. Edit and preview local resources.
  2. Run fluid portal doctor and project checks.
  3. Pull and reconcile remote changes.
  4. Push the complete working definition.
  5. Create a version.
  6. Activate the reviewed version.

Create a version

List available versions and record the ID you intend to activate:

Activate a version

Use --yes only when a non-interactive activation is authorized.
Activation changes the live portal. Do not activate as part of routine local validation or draft synchronization.

Recover from a failed release

If version creation or activation fails, inspect the remote version list before retrying. Do not create repeated snapshots until you know whether the prior command succeeded. The CLI also supports combined flags such as version create --activate and push --activate. Use the separate commands in automated or reviewed workflows so each remote effect remains visible.