← All releases · Published · superseded
release-data/0.1.1/notes.md.
Verity One vo-cli 0.1.1
First public packaged vo-cli cut.
What is this release?
vo-cli is the single-binary form of the Verity One CLI. Before this release the CLI shipped source-only: operators cloned the repository and ran it under a local Bun toolchain. Starting with 0.1.1 the CLI is also available as a signed, notarized macOS tarball suitable for direct download and install.
This release is scoped narrowly:
vo-clionly. The fullverity-one-appdesktop surface is not in this release.- macOS only.
darwin-arm64(Apple Silicon) anddarwin-x64(Intel). Linux and Windows are not in this release. - Source install remains fully supported. The packaged tarball is a parallel path, not a replacement.
Supported platforms
| Platform | Artifact |
|---|---|
macOS Apple Silicon (darwin-arm64) | vo-cli-darwin-arm64.tar.gz |
macOS Intel (darwin-x64) | vo-cli-darwin-x64.tar.gz |
Both tarballs are Developer ID signed and Apple-notarized. The signer Team ID for 0.1.1 is R54YNMS579. The Verity One engine pins that Team ID and refuses any artifact whose codesign trust chain does not match.
Install and update framing
Once the public release channel is live, a machine with Verity One already installed source-side can migrate to the packaged CLI without losing local graph state: packaged install writes a marker alongside the existing install root rather than overwriting the source tree. vo update against a packaged install checks the channel manifest and, when a newer version is published, fetches the corresponding signed tarball and swaps the binary atomically.
Self-update (the CLI updating itself in place without operator action) ships separately from this release; see docs/VO-PUBLIC-RELEASE-DISTRIBUTION-PR-LADDER.md for the ordered public release distribution sequence.
Integrity
Both tarballs have published artifact_sha256 values in this release's release-metadata.json and a matching public SHA256SUMS.txt. On machines running the Verity One engine the sha256 check happens automatically as part of the packaged install path. Operators verifying manually can run shasum -a 256 against the downloaded tarball and compare to SHA256SUMS.txt.
Source
This release was cut from commit 0d1beae54652a0fd4bf20b8251000b173620cdf5.
Staging note
At the time this release-data entry was committed, the branded public surfaces (download.verityone.app, releases.verityone.app) had not yet gone live. See release-data/README.md for how pre-publication entries become authoritative once the publication PR resolves the live URLs and publishes the artifacts.