Updating the Agent
How to update
Update with the tool you installed with, then restart ngris — a running agent keeps using the binary it started with. Check the result with ngris --version.
Homebrew, winget, install script
Homebrew and winget upgrade the package in place. The install script always installs the latest release (set NGRIS_VERSION to pin one), so running it again updates the agent. If ngris --version still shows the old version afterwards, an older copy comes first on your PATH: find it with command -v ngris, or reinstall into that directory with NGRIS_INSTALL_DIR.
Docker & Kubernetes
Pull the image again and recreate the container. An image pinned to an older tag (for example ghcr.io/ngris-edge/ngris:0.4.1) has to move to the new release.
brew upgrade --cask ngris
ngris --versionwinget upgrade Ngris
ngris --versioncurl -fsSL https://ngris.com/install.sh | sh
ngris --versiondocker pull ghcr.io/ngris-edge/ngris:latest
# then recreate the container (docker run … as before)Version policy
This ngris agent (v0.4.1) is too old. Update it: https://ngris.com/install. It does not retry: update it and start it again. An agent that is already connected keeps running until it reconnects, and every edge deploy reconnects agents.Minimum supported version
Ngris can also set a minimum agent version. An agent below it is refused the same way, with a message that names your version and the minimum, for example This ngris agent (<your version>) is older than the minimum supported version (<minimum>). Update it: https://ngris.com/install.
The minimum applies to the CLI's own commands too. ngris deploy, ngris apps … (including ngris apps env and ngris apps cron) and every other command that calls the ngris API are refused with 426 and a message such as This ngris CLI (v<your version>) is older than the minimum supported version <minimum>. Update: https://ngris.com/install. Update the agent and run the command again.