Release Readiness
What this page covers
A single pivot for "what shipped in release X, what remains in release Y, and what's the gate between them." Active release rows mirror live GitHub milestones. Future beta, release-candidate, and GA rows are gated horizons from ROADMAP.md, not active milestones. For the deeper version-string conventions, see ADR-001 and ADR-019.
The release-line lattice:
v0.9.0aN
Alpha series. Posture calibration + plugin extraction. v0.9.0a1 shipped 2026-05-08; v0.9.0a2 tagged 2026-05-18; v0.9.0a3 shipped 2026-05-22; v0.9.0a4 shipped 2026-05-22; v0.9.0a5 shipped 2026-05-22; v0.9.0a6 shipped 2026-05-23; v0.9.0a7 shipped 2026-05-23; v0.9.0a8 shipped 2026-05-23; v0.9.0a9 shipped 2026-05-25; v0.9.0a10 release candidate 2026-05-26.
v0.9.0a10
Active adapter-batch publication release candidate. Does not open beta, RC, GA, or a supported-plugin stability claim.
Future beta line
Hardened core, 30-day external operator soak. No active milestone today.
Future release-candidate line
Observation window after hardened-core exit. No active milestone today.
Future GA line
Wire format committed, compatibility commitment honored across the v1.x line. No active milestone today.
v0.9.0a10 — Adapter batch publication readiness
Active release candidate for adapter package publication, package evidence, and current release-line documentation.
v0.9.0a10 validates the Cognee, Gemini, Letta, OpenAI-compatible tools, and
Zep adapter packages as independently versioned 0.1.0 experimental plugins.
The release keeps adapter behavior opt-in, records package evidence, updates
current compatibility projections, and preserves the Trusted Publisher release
path before tag.
v0.9.0a9 shipped; adapter package records, manifests, and publication surfaces are complete.v0.9.0a10.v0.9.0a9 — Plugin discovery and publication readiness
Historical alpha release for plugin discovery, package evidence, and current release-line documentation.
v0.9.0a9 validated the public plugin catalog, scoped MCP npm publication
evidence, Trusted Publisher release path, current compatibility projections,
and release-line documentation. Experimental plugins remained opt-in and
unsupported unless a future ADR-008 graduation gate says otherwise.
v0.9.0a8 shipped; plugin publication readiness and MCP package evidence were recorded.v0.9.0a9.v0.9.0a8 — Multi-tenant scoping validation
Historical alpha validation release for multi-tenant plugin-boundary behavior.
v0.9.0a8 validates stigmem-plugin-multi-tenant as the opt-in boundary for
tenant scoping. Default installs collapse callers into the single default
tenant, while non-default tenant resolution remains inactive unless the plugin
is registered and explicitly enabled.
v0.9.0a7 shipped; Multi-tenant feature records and experimental source package exist for a8 validation.default, plugin-loaded tenant scoping validates, security projections align, package dry-runs pass, and the release published as v0.9.0a8.Future beta line — Hardened core
Hardened-core validation before any beta milestone opens.
Scope per ROADMAP future beta line: capability redesign, federation hardening, modular spec migration completion, OpenClaw safety, adversarial conformance corpus, storage immutability stack, operator-facing docs, and a 30-day external operator soak. No beta milestone is active today.
make demo / make demo-attack, contributor architecture path, issue templates, engineering log, good-first issue tagging.Future release-candidate line
Supply-chain hardening + external production usage.
Scope per ROADMAP future release-candidate and GA horizons: sigstore-signed releases, reproducible builds, SBOM publication, three or more external operators in production, wire-format freeze candidate. No release-candidate milestone is active today.
v1.0/; freeze finalizes at GA.Future GA line
Wire format committed; compatibility commitment honored across v1.x.
Scope per ROADMAP future release-candidate and GA exit criteria: stable release shipped, wire format committed, compatibility commitment doc per ADR-013 honored across the v1.x line.
How readiness is enforced
Three gates ensure release notes match shipped code:
- PR-closes-issue and milestone discipline (CONTRIBUTING.md) — every release-scoped PR from v0.9.0a3 onward must close exactly one issue and use the issue's matching milestone. Lets anyone answer "what shipped in release X?" by reading the milestone view.
scripts/check_release_readiness.py— umbrella gate that asserts the CHANGELOG[<version>]section is non-empty and the corresponding milestone has zero open issues. Runs as arelease-readinessjob in.github/workflows/publish.ymlahead of every tag-gated publish job.- Existing per-artifact gates —
check_version_consistency.py,validate_version_surfaces.py,check_release_evidence.py, and the coverage/ruff/mypy/security-doc baselines — all run as part of CI.
Updated as releases land. Last updated: 2026-05-21.