qa release and replace the binary you are
running.
For an npm installation, run npm install -g qa@latest instead. qa upgrade
prints the npm update command without replacing the installed binary. Update
project dependencies with your project’s package manager.
Behavior
- Reads the latest version from the release manifest.
- Downloads the binary for your OS, CPU, and libc (the same selection the installer makes).
- Verifies the download against its published SHA-256 checksum.
- Installs the verified file as
qain the directory holding the current executable.
0.
The current updater renames an install still named mo to qa in the same
directory and removes mo. An older updater can install the new release without
renaming the file. Run mo upgrade, check qa --version, and run mo upgrade
again if qa is still missing. The second run uses the new updater. If the
binary is already on the latest release, it renames the file without downloading
anything. If mo cannot be deleted, qa doctor flags the leftover file.
Arguments
string
Install this exact version instead of the latest release, for example
qa upgrade 1.4.2. Downgrades are allowed.Upgrade prompt
For standalone installations, interactive commands show an update notice when a newer release exists and ask:--json, on qa upgrade, qa version, qa skills, qa licenses, or
qa doctor, or when NO_UPDATE_NOTIFIER or MOMENTIC_SKIP_UPGRADE_PROMPT is
set. After it is shown once, it stays quiet for that version for 24 hours.
Notes
- The command needs write access to the directory that holds the installed
binary (
~/.local/binby default). If the install directory is not writable, re-run the installer instead:curl -fsSL https://cli.momentic.ai/qa | sh. qa upgradeonly works on a released binary. A source checkout run throughbunreports that it cannot self-update.