Updates and maintenance

Check for Hokan releases, choose a release channel, and maintain local history.

Bash
hokan doctor --jsonhokan history statshokan history repairhokan history compacthokan spec listhokan upgrade --check

Writable release-installer binaries can update themselves from GitHub releases. Updates download the matching archive, verify SHA256SUMS, run a binary smoke test, back up the current executable, and replace it atomically.

Bash
hokan upgradehokan upgrade --channel beta

Each new Hokan session can start a silent background check and install a newer release. Checks and failed retries are limited to once every 30 minutes; running sessions keep their current binary, and the update takes effect on the next launch. Updates use an installation lock, keep a .bak backup, and stage beside the installed binary so a cache on another disk works too.

New beta installations default to the beta channel; stable builds default to stable. An explicitly configured channel is preserved. Existing beta users whose config says channel = "stable" can opt into beta updates once with:

Bash
hokan upgrade --channel beta --yes

Set HOKAN_NO_AUTO_UPDATE=1 to disable automatic updating for one session, or configure [update] (set enabled = false to disable it persistently):

TOML
[update]enabled = truechannel = "beta"interval_secs = 1800