CLI

# hotcfg promote

Copy the latest version of one environment to another, checked against the schema.

usage

```
hotcfg promote <bin_id> --from <env> --to <env>
```

Copies the latest version of `--from` to `--to` as the next version there, after checking it against the bin's schema. The edge cache for `--to` is purged.

terminal

```
$ hotcfg promote mobile-flags --from staging --to production
✓ Promoted mobile-flags staging v2 → production v1
  hash     7ac562a24ad09d989d7a8cc810d64bd108028f013313b206aafba5c182fb951d
  cache    edge purge queued for production
```

Version numbers are per environment, so staging v2 can become production v1.

## Flags

| Flag | Default | Description |
| --- | --- | --- |
| `--from` | required | The source environment. |
| `--to` | required | The target environment. Must differ from `--from`. |

A [limited key](https://hotcfg.run/docs/reference/keys) needs both environments. A common setup is a CI key limited to `staging`, and promoting to production from a person's machine, the dashboard, or a job that needs approval: see [Config from CI](https://hotcfg.run/docs/guides/ci#promote-with-approval).

Last updated 5 November 2026
