ankra upgrade
Download and install a specific Ankra CLI release, replacing the currently running binary in place. By default the command upgrades to the latest stable release. Install an exact release with--version (for example --version v0.2.5, or --version
0.2.5). When a version is pinned the command installs it whether it is
newer, older or the same as the running binary, so --version doubles as a
downgrade: ‘ankra upgrade --version v0.1.9’ rolls back to that release.
Use --check to report whether a newer release is available without
installing anything.
When the beta channel is enabled (see ‘ankra config beta enable’) the
newest release including pre-releases (release candidates such as
v0.3.0-rc.1) is installed instead. Use --beta or --beta=false to override
the saved channel for a single run.
The downloaded binary is verified against its published SHA-256 checksum
before it replaces the existing executable.
The Ankra agent skills (‘ankra skills install’) ship inside the binary, so
an upgrade also offers to refresh the copies already installed for your
assistants; the new binary reinstalls them once it is in place, with the
same --no-rules, --no-workflows and --with-hooks choices each install was
made with. --skills takes the offer without asking and --skills=false
declines it. --yes skips only the upgrade confirmation: a scripted
‘ankra upgrade --yes’ leaves the installed skills as they are and says how
to refresh them; pass --yes --skills to refresh them without any question.