Updates & channels

aircode update --check      # is there something new on my channel?
aircode update              # download, verify, install, switch
aircode update --rollback   # instant switch back to the previous version

What an update actually does

1. Fetches the signed channel manifest and verifies its Ed25519 signature — an unsigned or tampered manifest is rejected outright.
2. Downloads the release tarball, checks its sha256 (and signature).
3. Installs to ~/.aircode/versions/<new> next to the current version.
4. Atomically switches the current symlink.
5. Restarts the server — running agent sessions are not touched. They live in tmux, and the systemd unit uses KillMode=process: only the server process restarts.

Because versions sit side by side, --rollback is a symlink switch, not a reinstall. The two most recent versions are kept; older ones are purged.

Channels

• stable — the default.
• beta — earlier features, same signing and update mechanics: aircode update --channel beta, or set "updateChannel": "beta" in the config file.

Update notifications

The server checks its channel once a day and surfaces available updates in the UI and in aircode status. It never applies updates by itself — updating a server you operate is your call, always.

Data compatibility

Data migrations are forward-only. Rolling back across a schema-changing release is flagged in the release notes — check them before --rollback after a major update.