@blotout/qinto-cli 0.1.1 → 0.1.3

package/README.md

@@ -10,6 +10,20 @@ npm i -g @blotout/qinto-cli
 
 Needs Node.js 24 or newer. The command is `qinto`.
 
+## Stay up to date
+
+```sh
+qinto update
+```
+
+`update` asks npm for the newest published version and, when that is newer than the one running, installs it with the package
+manager that installed the CLI — npm, pnpm, yarn, or bun, each detected from the install path. An `npx` run and a source checkout
+have nothing to update, and the command says so instead of installing anything.
+
+Every other command also checks for a new version, at most once a day, and prints a yellow notice on stderr when one exists. The
+notice never appears in machine mode (`--json`, `--no-input`, or a non-terminal stderr), so piped and agent-driven output stays
+clean. `NO_COLOR` drops the colour; `QINTO_NO_UPDATE_CHECK=1` turns the check off altogether.
+
 ## Log in
 
 ```sh
@@ -327,6 +341,7 @@ Every interactive path has a non-interactive equivalent. This is a standing rule
 | `--no-browser` | `login` prints the authorize URL instead of opening a browser; open it in a browser on the same host so its loopback callback reaches the CLI. |
 | `QINTO_API_TOKEN` | A bearer token that takes precedence over stored logins. Works with team API tokens (`qapi_`, from Team → API tokens in the Qinto platform) and OAuth access tokens (`qoa_`). No browser needed. |
 | `QINTO_ENV` | `production` or `sandbox` for every command in the shell — the non-interactive stand-in for `qinto env`, which stores the same choice. |
+| `QINTO_NO_UPDATE_CHECK` | Any non-empty value stops the daily new-version lookup. Machine mode already suppresses it, so a script needs this only to keep the CLI off the network. |
 | Exit codes | `0` success, `1` operational failure, `2` usage error, `130` aborted prompt (Ctrl-C). Errors go to stderr; with `--json` they are printed as `{"error": "…"}`. |
 
 ## Environments