Flux

Releases

The release workflow — from draft to deployment, with review, approval, and rollback.

Release lifecycle

A release moves through a defined set of states:

  1. Draft — the release is being assembled. Changes are selected and the scope is defined.
  2. Open — the release is ready for review. Team members can inspect the diff, leave comments, and approve or request changes.
  3. Deploying — the release has been approved and deployment is in progress. Changes are being written to target stores.
  4. Deployed — all changes have been applied successfully.

A release can also be cancelled at any point before deployment completes, or marked as failed if deployment encounters an unrecoverable error.

Release types

  • Objects — deploys store data only (products, collections, pages, menus, etc.)
  • Theme — deploys theme file changes only
  • Hybrid — deploys both store data and theme changes in a single release

Creating a release

To create a release:

  1. Navigate to Releases in the dashboard
  2. Select your source and target environments
  3. Flux captures the current state of both environments, computes the diff, and presents it for review

For time-sensitive changes, quick deploy mode bypasses the review step and deploys directly. Useful for hotfixes, but skips the approval workflow.

Review and approval

Releases can require approval before deployment:

  • Approval rules define which groups can approve and how many approvals are needed
  • Status checks integrate with GitHub for automated validation
  • Reviewers can approve, request changes, or dismiss reviews (with appropriate permissions)

Configure approval rules in Settings → Approvals.

Deployment

When a release is deployed, Flux applies changes to the target store:

  1. Validation — the changeset is validated against the target environment
  2. Dependency resolution — objects are ordered by their dependencies (e.g., definitions before entries, blogs before articles)
  3. Execution — changes are applied in dependency order to maintain referential integrity
  4. Verification — the target state is verified against the expected outcome

Each operation is tracked individually with its status (pending, applied, skipped, failed, reverted), so you can see exactly what happened.

Rollback

Any deployed release can be rolled back. Flux creates a revert release from the pre-deployment state and applies it as a new deployment. Both the original and the rollback are recorded as separate releases, maintaining a complete audit trail.

Next steps

Next

Deployments →