CLI

# hotcfg rollout

Change the share of a progressive rollout, complete it or abort it.

usage

```
hotcfg rollout <bin_id> [--env <env>] (--percent <1-99> | --complete | --abort)
```

Changes a [progressive rollout](https://hotcfg.run/docs/guides/rollouts) that [`hotcfg promote --percent`](https://hotcfg.run/docs/cli/promote#roll-out-gradually) started. Each change purges the environment's edge cache.

terminal

```
$ hotcfg rollout mobile-flags --percent 50
✓ Rolling out mobile-flags production v13 to 50%; the rest get v12
  cache    edge purge queued for production

$ hotcfg rollout mobile-flags --complete
✓ Rollout completed: mobile-flags production is now v13 for everyone (was v12)
  cache    edge purge queued for production
```

Needs CLI 0.4.0 or later and a secret key that can write the environment.

## Flags

Give exactly one of `--percent`, `--complete` or `--abort`.

| Flag | Default | Description |
| --- | --- | --- |
| `--env` | `production` | The environment with the rollout. |
| `--percent` |  | Give the new version to this share of readers, from 1 to 99: apps that send `?bucket=` below it. |
| `--complete` | off | Give the new version to everyone. It becomes the environment's current version. |
| `--abort` | off | Give everyone the current version again. The new version stays in history. |
| `--json` | off | Print the API's response as JSON. |

With no rollout running, it fails with `no rollout running` (HTTP 409).

Last updated 17 November 2026
