# pyre CLI changelog All notable changes to the `pyre` command-line client. Versions follow semver; the tag is `cli-v`. ## 1.0.7 — 2026-09-23 - `pyre volume create --encryption customer` works and is documented (the 1.0.0–1.0.6 example said `customer-key`, which the API refuses; it is now accepted as an alias of `customer`, as are `none`/`off`). Any other value is refused with exit 2 and the two choices, before anything is sent. After creating an encrypted volume the CLI says where the key file will be made (`pyre appliance deploy`, `~/.pyre/.key`) and that losing it makes the volume unrecoverable. - Every input is checked against the API's own rule before a request is built: ids in paths are numeric; volume, recovery and view names, labels, policies, points in time, `--since`, `--type` (now also `nfs+smb`), `--os`, `--cache-mb`, `--store`, store fields, emails and URLs (`--api`, `api_base`, `download_base`, `--endpoint`) are validated; a bad value is a usage error (exit 2) naming the choices. Validated path segments are additionally percent-escaped. - `pyre store probe|add`: the provider list is the API's (`aws`, `wasabi`, `minio`, `weka`, `other`; default `other`). The old default `s3` and the documented `backblaze` were refused by the server on every call. - Exit codes: cobra's own parse errors (`unknown shorthand flag`, `flag needs an argument`) are usage errors (exit 2, was 1); a stray word after a group command (`pyre volume nosuch`) is a usage error (was help with exit 0). - A server-side validation answer (HTTP 422) is rendered as `field: message`, not as a JSON dump. - Tests: the customer command matrix (`internal/cmd/permutations_test.go`, over 220 rows: valid, invalid and injection cases against a fake control plane) and new smoke checks against the real API; design and pass/fail criteria in `docs/CLI-TESTING.md`. ## 1.0.6 — 2026-09-23 - Encryption is shown as "customer key" or "none" from the API's `encryption` field (server section 10); a server that does not send the field shows "unknown" instead of a false "none". Also fills the `pyre volume list` ENCRYPTION column. ## 1.0.5 — 2026-09-23 - `pyre update` says which file it replaces ("replacing /path/pyre"), checks that directory is writable BEFORE downloading and names it in the error (with `sudo pyre update` only when that path needs it), and after updating lists any other `pyre` on PATH it did not touch. `pyre version` shows the binary's path and any others on PATH. - Sizes match the dashboard: decimal GB with one decimal (26843545600 bytes → 26.8 GB); appliance measurements that arrive as strings are formatted too (no more raw byte counts). - `volume show` / `volume status`: the Offline line appears only while the appliance is offline; buffer fill and disk-low facts sit on the Sync line otherwise, and an empty buffer is not mentioned. ## 1.0.4 — 2026-09-23 - `pyre volume show` is readable: one line each for Volume, Appliance, Sync, Offline, Storage, Errors and Measured, sizes in the dashboard's units, times local. Nothing in table mode prints raw JSON any more (nested data becomes dotted lines); `-o json` is unchanged, `-o plain` flattens to `keyvalue`. - New `pyre volume status `: the live block alone, with `--watch [--every 5s]` redrawing until Ctrl-C on macOS, Linux and Windows (no watch(1) needed). - `pyre appliance status` uses the same rendering. - `pyre completion` without a shell now says `pyre completion — e.g. pyre completion zsh`. - `pyre update` rewrites the completion files it finds (bash, zsh, fish, PowerShell) with the new binary, clears stale `~/.zcompdump*`, and says when zsh completion is installed but `~/.zshrc` does not load it. ## 1.0.3 — 2026-09-23 - Homebrew: the generated formula carries a top-level `url` so current Homebrew accepts the tap (it validates every platform, Linux arm64 included, and refused 1.0.2's formula with "requires at least a URL"). No change to the binary. ## 1.0.2 — 2026-09-23 (1.0.1 was tagged on the same day but never published: its installer still had the PATH gap below. Everything listed here is new since 1.0.0.) - install.sh: installs into /usr/local/bin through sudo (the password prompt works under `curl | sh`); the ~/.local/bin fallback now adds itself to PATH and the zsh completion dir to fpath in your shell rc, and ends with "Open a new terminal (or run: source ~/.zshrc)". Found by the first real install on a Mac: `pyre` was not on PATH. - Token lifecycle: `pyre auth token create --expires 30d|1y|never` (server default 90 days), `list` shows state and expiry, `remove` deletes a revoked or expired row (`--force` revokes first), `prune` drops every such row. Operators: `pyre admin tokens list|revoke|remove|prune` across tenants. - `pyre uninstall` now removes every man page it installed (`pyre-.1.gz`), not only `pyre.1.gz`. - Install docs: `brew trust pyredata/pyre` before `brew install pyre` (current Homebrew refuses formulae from an untrusted tap). ## 1.0.0 — 2026-09-23 First packaged release, a rewrite in Go of the 0.1 Python prototype. - One static binary per platform: macOS (Apple Silicon and Intel), Linux x86-64, Windows x86-64. - Install channels: apt repository (signed), Homebrew tap, `curl | sh`, PowerShell one-liner, Scoop manifest, plain archives. - `pyre update` (signed releases, in-place replace; defers to apt / Homebrew / Scoop when they installed it) and `pyre uninstall`. - Shell completion for bash, zsh, fish and PowerShell; man pages. - Scripting: `-o json` / `-o plain`, `--yes`, stable exit codes, `pyre batch` to run a file of commands with one login. - Profiles for more than one control plane (`--profile`, `pyre config`), `--ca-cert` / `--insecure` for self-hosted managers, every host a config value. - Customer commands: auth (token per user), volume (incl. deleted volumes), restore-points, restore, recovery, view, history, snapshot, appliance (deploy/mount/remove/status/disconnect/flush/cleanup), store (bring your own S3), account. - Operator commands (`pyre admin`): hubs (scan/add/preflight/build/ promote/demote/remove/bootstrap/...), users (approve/reject/delete), tenants.