← All releases · Staged · pending publication
release-data/0.2.0/notes.md
in the Verity One repository. The release data was committed for
review under VO-RELEASE-DATA-SOURCE-OF-TRUTH-PR-1,
but publication — flipping the stable channel manifest and going
live on this domain — happens in a later dedicated PR. Nothing on
this page is a claim that the release is fetchable from the branded
URLs today.
Verity One 0.2.0
Source-install stable cut of the open-core Verity One node, re-synced to the current upstream line.
What is this release?
0.2.0 is the current stable release of the open-core Verity One local node — the graph engine, the knowledge miners, and a local MCP server. It is a **source install**: there are no packaged binaries in this release. The supported install path is the one-command source bootstrap.
It re-syncs the open-core repository to the current upstream line, preserving the open-core boundary (hosted / multi-tenant VO+ modules stay stubbed) and bringing in the accumulated node hardening since 0.1.2.
How to install
curl -fsSL https://verityone.app/install.sh | sh
The installer clones the public repository at the pinned source ref, runs bun install, and prints the next steps. One-time database setup is bun run db:setup (applies db/schema.sql; no embedding-provider key required). Full onboarding lives at https://verityone.app/start.
What changed since 0.1.2
- SSE client-slot leak fix in the World Ingestor monitor (slots are now released on every disconnect path, not just a clean abort).
- Memory write de-duplication is now race-safe: the de-dup check runs inside the write transaction's advisory lock, so two concurrent identical writes collapse to a single node.
- Ingestion corroboration boosts are gated on verified provenance, so unverified or injected content cannot inflate an existing node.
- An SSRF guard, request body-size caps, an embedding-availability honesty check, and an optional operations-alert poller.
- Installer hardening: the pinned ref is resolved to a concrete commit and checked out detached, so a re-run can never silently keep stale local code.
What is pinned
| Field | Value |
|---|---|
| Channel | stable |
| Install mode | source |
| Public repo | github.com/markprobinson3-maker/VerityOne |
| Source ref | 1433591482eb6ed069862129eff45d6c4e7ae7ab |
The machine-readable channel manifest is served from verityone.app/releases/stable.json and is Ed25519-signed; the install.source_ref above is verified to be publicly reachable before the manifest is published.
What is not in this release
- No packaged binaries (no signed
vo-clitarballs). Source install is the only supported path for the stable channel today. - No hosted / multi-tenant features. Those (
VO+) are a separate, optional layer and are not part of the open-core repository.
Scope
This release covers the local, self-hostable node only. The local MCP server lets MCP-capable agents query and write the graph. Everything core runs on your machine; the local node remains the source of truth.