Skip to content

v0.23.0 release readiness: scope, testing, docs, ship checklist #1288

Description

@phernandez

Single tracking issue for everything between here and just release v0.23.0. Milestone ledger: 111 closed items; feature work is complete — what remains is one validation build-out (#1248), scope decisions, changelog refresh, verification, and choreography.

1. Scope decisions (settle first)

Landed 2026-08-21 during make-ready: #1290 (ChatGPT import, closes #1276 — codex loop hardened it 4×: Windows CRT sentinel, deterministic epoch, UTF-8 400s, immutable message-time rung), #1291 (prose-tail relations, the #1260 slice), #1292 (dev-release pipeline), #1289 (changelog). Benchmark driver: basic-memory-benchmarks PR #42, small-scale validated; its first catch — acknowledged edit_note appends lost to LWW across concurrent MCP sessions — is flagged on #1248 for a product decision.

2. Remaining build item

  • Comprehensive v0.23 benchmark: indexing at scale, Redis reads, reranked search #1248 — comprehensive benchmark: indexing at scale + Redis reads + reranked search + multi-agent composite, v0.22.1 vs v0.23 (needs concurrent-writer driver in basic-memory-benchmarks). Honest claims only: MRR 0.616→0.719 (+17%) rerank-on and correctness under concurrency (v0.22.1 deadlocks/duplicates). Do NOT claim ">50% faster" for v0.22.1→v0.23.

3. Testing / verification

4. Docs

5. Release day (in order)

6. Post-release

  • basic-memory-cloud: re-pin the basic-memory git rev to the released tag
  • docs.basicmemory.com: What's New page under content/2.whats-new/ + version badge in content/index.md
  • MCP Registry: mcp-publisher publish from repo root
  • Verify Homebrew formula + OpenClaw npm publish (automated; confirm)
  • Announcement: Discord; optional blog post on basicmemory.com (significant release — reranking, retrieval inspector, concurrency rebuild, Team sync)

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions