Repository navigation
1.7.1 - 2026-10-12
Release Notes
Added
- LICENSE file. The Elastic License 2.0 text (the same file as the Vericto
engine and proxy), whichCargo.tomlalready declared asElastic-2.0. It
ships in the release archives, the@vericto/vericto-clinpm package (whose
publish step now refuses a package without it) and the container image
(/usr/share/doc/vericto/LICENSE, with the
org.opencontainers.image.licenses=Elastic-2.0label, empty in 1.7.0).
Changed
- Dependencies: clap 4.6.7, clap_complete 4.6.11, tokio 1.53.2, serde 1.0.229,
serde_json 1.0.151. - CI actions: actions/setup-node 7.1.0, docker/setup-qemu-action 4.4.0,
docker/login-action 4.6.0, docker/metadata-action 6.2.0,
docker/build-push-action 7.4.0.
Fixed
- The container image is tagged
latestonce, and only for a release:
prerelease tags no longer movelatest. - A manual run of the Docker workflow on a branch builds the image instead of
failing; only a version tag publishes and attests it. - The integration tests no longer read the developer's own
~/.config/vericto/config.toml: each run of the binary gets an empty temp
HOME/XDG_CONFIG_HOME, so a stored login on macOS no longer fails them.
Install vericto-cli 1.7.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/vericto/vericto-cli/releases/download/v1.7.1/vericto-cli-installer.sh | shInstall prebuilt binaries into your npm project
npm install @vericto/vericto-cli@1.7.1Download vericto-cli 1.7.1
| File | Platform | Checksum |
|---|---|---|
| vericto-cli-aarch64-apple-darwin.tar.xz | Apple Silicon macOS | checksum |
| vericto-cli-x86_64-apple-darwin.tar.xz | Intel macOS | checksum |
| vericto-cli-x86_64-pc-windows-msvc.zip | x64 Windows | checksum |
| vericto-cli-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| vericto-cli-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo vericto/vericto-cliYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>