Knolo Release Records: Test, Stamp, Publish, Then Record
How the open-source Knolo project shipped eight npm packages in four public steps, and why separate release records help anyone who pins Knolo versions.
Knolo is the open-source, local-first Knowledge Image runtime and format, released under Apache-2.0 with @knolo/core on npm and source in the Knolo core repository on GitHub. An open format is only as trustworthy as its release history. On 16 November 2026 the Knolo project published eight packages to npm, and it did so in four separate, public steps. This note walks through those steps and why they matter for anyone who pins Knolo versions.
Step 1: Knolo records the test run before any version stamp
Pull request #194 wrote down a local test run of main at commit 9d58d66 on Node v22.14.0, before any package version changed. It records the counts: Exchange 17 passed; CLI 113 passed, 1 skipped (an optional live Hub smoke test), 0 failed; MCP 28, AI SDK 7, Mastra 7, OpenAI Agents 4 and n8n 15 passed. The release:check script passed across 303 Markdown files.
It also records what was not tested directly: @knolo/tools has no test script of its own and is built by the host suites. Writing down the gap is part of the record.
Step 2: Knolo stamps versions without publishing
Pull request #195 changed package files only. It set @knolo/exchange 0.1.1, @knolo/tools 0.2.2, @knolo/mcp 0.2.4, the AI SDK, Mastra and OpenAI Agents adapters to 0.1.1, n8n-nodes-knolo 0.1.1 and @knolo/cli 6.2.8, with each dependency floor stated. It says plainly that it does not publish and that npm latest is unchanged.
It also lists what was not bumped: @knolo/core stays 6.2.3, and Box, OpenClaw, LangChain, LlamaIndex, the Rust and Python runtimes and the ICP canister keep their versions. Listings that name published packages stay on the old pins until a record exists after the upload.
Steps 3 and 4: Knolo publishes, then records what npm says
After the upload, pull request #196 recorded the eight npm latest versions and moved the published pins. For each package it states what the previous tarball lacks, for example that @knolo/mcp 0.2.3 has no KITE evaluate or verify tools and @knolo/cli 6.2.7 has no knolo exchange relay. The batch has no git tag and no GitHub Release, and the record says so rather than leaving readers to guess.
Why Knolo separates the steps
Each step answers a different question for someone downstream:
- Was it tested? The pre-publish record names the commit, runtime and counts.
- What is about to change? The stamp shows every version and floor before anything is public.
- What is actually on npm? The post-publish record is written after the fact, against the registry.
- What did the old version lack? The "previous tarball" column tells a pinned user whether upgrading matters.
This is the same idea Knolo applies to Knowledge Images themselves: a digest-pinned artifact and a receipt you can check, rather than a claim you have to trust. A release history built the same way lets compatibility be read from public records instead of announcements.
Where Knolo lifecycle status lives
The Knolo lifecycle page defines the intended states (proposed, active, maintenance, deprecated, archived) and states that a per-project lifecycle matrix has not been published yet. Until it is, the repository records above are the working source of truth. Related pages: Knolo supported versions, Knolo compatibility and Knolo transparency.
Learn more about Knolo
knolo · open technology · lifecycle · releases · transparency
