Pick the row that matches how each component was installed. After bumping the server, run mantis doctor to confirm CLI/server compatibility.
One-time step when upgrading to ≥ v0.1.2: the server now requires MANTIS_API_KEY_PEPPER, a base64 secret used as the HMAC key for hashing API keys at rest. Generate one with openssl rand -base64 32 and set it in your .env (or your PaaS secret store) before redeploying. Existing API keys keep working — the verifier accepts the old pre-pepper SHA-256 form and opportunistically upgrades each row on next use. Skip this step and the server will refuse to boot with a clear “Missing required env: MANTIS_API_KEY_PEPPER” message. See Configuration → Required for the full rationale.
To get notified of new releases, Watch → Custom → Releases on the GitHub repo — cli-v* tags publish CLI binaries, plain v* tags publish server releases.