CLI

# hotcfg unpublish

Stop serving an environment while keeping its history.

usage

```
hotcfg unpublish <bin_id> --env <env>
```

Reads of the environment answer `404` from now on, and the edge cache is purged. Every version is kept: pinned reads (`?v=3`) still work, and a rollback or a push publishes again.

terminal

```
$ hotcfg unpublish mobile-flags --env staging
✓ Unpublished mobile-flags (staging): v2 is no longer served
  history  kept; publish again with 'hotcfg rollback mobile-flags --env staging --to 2'
  cache    edge purge queued for staging
```

## Flags

| Flag | Default | Description |
| --- | --- | --- |
| `--env` | required | The environment to take down. There's no default, on purpose. |

Note

Apps that follow the [fetching recipes](https://hotcfg.run/docs/guides/fetching) keep using their last good copy when a read answers `404`, so unpublishing doesn't wipe config from devices that already have it.

To delete the versions too, use [env delete](https://hotcfg.run/docs/cli/env-delete).

Last updated 5 November 2026
