Guides

Staging, promote and rollback

Test a change in staging, promote that exact version to production, and roll back if needed.

Every bin has development, staging and production. Each has its own numbered history.

Promote

Promoting copies one environment's current version to another. The copy is checked against the schema and becomes the next version there: what you tested is exactly what ships.

terminal
hotcfg diff mobile-flags --env staging --from v3 --to latest   # what changed
hotcfg promote mobile-flags --from staging --to production

In the dashboard, Promote shows the diff against the target before you confirm.

Roll back

A rollback publishes an earlier version again, as a new version. History is append-only, so you can always see what happened and roll forward again.

terminal
hotcfg history mobile-flags --env production
hotcfg rollback mobile-flags --env production --to 3

Apps pick up the rollback on their next fetch. A version older than your plan keeps can't be restored (404 version_pruned).

Unpublish and delete

ActionCLIEffect
Unpublishhotcfg unpublish mobile-flags --env stagingStop serving the environment. History is kept; a rollback publishes it again.
Deletehotcfg env delete mobile-flags --env developmentDelete the environment and its whole history. The next publish starts again at v1.

After either one, reads of that environment answer 404 with "environment has no published version".

Last updated 5 November 2026