hyperframes upgrade

hyperframes upgrade updates the CLI in place. It replaces the binary that invoked it and, if a project is in scope, bumps the version pin in package.json. Determinism is per-version, so plan upgrades like you would any encoder bump.

Synopsis

hyperframes upgrade [flags]

When run inside a project, the local install is updated. When run globally (-g), the global install is updated.

Flags

Common invocations

$ hyperframes upgrade --check
current  1.4.2
latest   1.5.0 (stable)
run "hyperframes upgrade" to install

JSON output

{
  "command": "upgrade",
  "status": "ok",
  "exit_code": 0,
  "channel": "stable",
  "from": "1.4.2",
  "to": "1.5.0",
  "pinned": true,
  "duration_ms": 3120
}

--check returns the same shape with status: "available" (or "current") and no install side effects.

Exit codes

• 0 — upgrade complete, or already on the latest version.
• 1 — network failure, permission denied, or the requested version does not exist.

Tips

• Always run hyperframes lint and your golden-file tests after an upgrade. A new encoder default can change every byte.
• In CI, prefer a hard --to <version> so the build is reproducible regardless of when it runs.
• --check is the only upgrade invocation that is side-effect free. Wire it into a weekly bot for nudges.
• The CLI never auto-upgrades itself. Every change to the binary is driven by an explicit upgrade call.

Next

• HyperFrames CLI — full command index.
• hyperframes doctor — verify the new install before you ship.