Release Notes

The CLI and the local gateway ship as one package. Every published version, with its downloads and checksums, is on the Verdictan packages releases page.

Find your installed version

verdictan --version

Compare it with the latest release. Downloading a new binary doesn't change a gateway that is already running; it keeps the old version until you restart it.

Update a gateway

1. Note the installed version, and keep a copy of the gateway's configuration.
2. Install the new version with the installation instructions for your method.
3. Restart one test gateway on the new version.
4. Send an ordinary request and one your policies block, and check the responses, the events, and the active configuration.
5. Only then update the other gateways.

For a gateway installed as a service, verdictan gateway upgrade plan, apply, status, and rollback do this with a health check and a way back; see verdictan gateway. Pin a version or image digest when you need reproducible deployments.

Files in a CLI release

A CLI version identifies the binary and the gateway runtime inside it. It says nothing about which Console or control-plane API version is deployed. For what each interface supports, see the Support Matrix.