v0.9.0a5 — preview alpha
Pre-release
Pre-release
Published artifacts:
- PyPI:
pip install --pre stigmem-py==0.9.0a5(also:stigmem,stigmem-node,stigmem-openclaw) - npm:
npm install @eidetic-labs/stigmem-ts@0.9.0-alpha.5 - GHCR:
docker pull ghcr.io/eidetic-labs/stigmem-node:0.9.0a5(also:0.9.0-alpha.5) - Supply-chain evidence: GHCR image is keyless-signed with Sigstore/cosign; SBOM and BuildKit provenance are attached as OCI referrers. Verification instructions: https://docs.stigmem.dev/operators/release-verification
- GPG signatures: The release tag is maintainer-signed. Detached artifact signatures may be uploaded manually after publication.
[0.9.0a5] — 2026-05-22
Status: preview alpha — pre-stable, not for production federation across
organizational boundaries. RTBF tombstones remain experimental, opt-in, and
operator-gated.
Per-ecosystem version strings (per ADR-019):
- PyPI / Python:
stigmem 0.9.0a5,stigmem-py 0.9.0a5,stigmem-node 0.9.0a5, andstigmem-openclaw 0.9.0a5(PEP 440). - npm / Node:
@eidetic-labs/stigmem-ts@0.9.0-alpha.5(semver). - GHCR:
ghcr.io/eidetic-labs/stigmem-node:0.9.0a5and:0.9.0-alpha.5. - Git tag, GitHub release, prose:
v0.9.0a5(shorthand).
Changed
- Advanced the enforced release-version surfaces to the
v0.9.0a5alpha line
across Python packages, npm packages, API metadata, conformance metadata,
plugin compatibility defaults, release documentation, and current-facing
adopter guidance.
Security
- Validated the
v0.9.0a5RTBF tombstone alpha scope as an opt-in
stigmem-plugin-tombstonesfeature. Default installs remain inert until the
plugin is registered and operator gates are enabled; admin issuance,
federation signer authority, forged-signature rejection, audit events,
selective revocation, legal-hold silence, and no-leak behavior are covered in
the feature-owned evidence record. - Consolidated admin determination to use
Identity.is_admin()across
tombstone admin routes, instruction admin routes, and provenance tombstone
filtering. This removes thecan_write() and can_federate()proxy so admin
checks consult the dedicatedadmincapability andcapability_checkvoting
hook consistently. - Added
scripts/check_admin_determination_consistency.pyto reject future
capability-combination-as-admin-proxy patterns in the Python node source.