docs: v0.23.0 release documentation - #42
Conversation
- Document bm inspect chunks and bm inspect query (basic-memory #1249/#1250) in the CLI reference, add an Inspecting retrieval section and FAQ pointer to Semantic Search, and mention the inspector in the changelog. - Correct Team workspace push/pull for the WebDAV transport (#1263): Team transfers no longer use bm cloud setup or storage credentials; each request is authorized per project (read to pull, edit to push). Updated Cloud Sync, Cloud CLI, and the CLI reference. - Mention list_directory sorting (#1268) in the MCP tools reference and broaden the FTS relaxation note to non-Latin scripts (#1269). - Add Known issues in v0.23.0 to the upgrade guide: FastEmbed asymmetric model prefixes (#1264, fix tracked for v0.23.1) and macOS file-identity edge cases (#1275, #1281), plus a troubleshooting entry for duplicate notes on macOS. - Renumber What's New pages so the upgrade guide no longer shares the 2. prefix with the Teams page (routes unchanged). Signed-off-by: phernandez <paul@basicmachines.co>
The prefix configuration is now the documented, supported setup for asymmetric FastEmbed models (#1264 closed by basic-memory#1302); automatic per-model-family defaults remain tracked in #1284. Signed-off-by: phernandez <paul@basicmachines.co>
Add /whats-new/v0-23 as the first What's New page, covering reranked semantic search (MRR 0.616 -> 0.719 with rerank on), pluggable vector indexes with first-party Milvus, the concurrency-safe indexing core, the bm inspect retrieval inspector, Team workspace push/pull over WebDAV, the bm config / diagnostics / bm hook operator surface, cloud share/prune/Redis additions, and the automatic migrations with a link to the upgrade guide. Renumber the whats-new pages with zero-padded prefixes so the new page sorts first and 10/11 sort after 9 (routes unchanged - Nuxt strips numeric prefixes). Point the welcome-page What's New callout at the new page instead of the changelog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G4rbaeHJN3L7CREp5v38J9 Signed-off-by: phernandez <paul@basicmachines.co>
Signed-off-by: phernandez <paul@basicmachines.co>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c3eba72883
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Reindex after every index switch | ||
|
|
||
| Run an incremental embedding rebuild immediately after changing `semantic_vector_index`: |
There was a problem hiding this comment.
Clean the old index before changing vector backends
For a Postgres project that already has embeddings, this ordering tells the operator to change semantic_vector_index and then reindex, but the same guide later states that foreign-owned manifest rows make the operation fail with SemanticVectorIndexExtensionError and must be removed while the previous index is still configured (lines 125–130). Following this primary procedure therefore puts the normal pgvector-to-Milvus migration into the documented recovery path; instruct users to perform the backed-up vector/manifest cleanup before changing the setting, or explain the exact conditions under which cleanup is unnecessary.
Useful? React with 👍 / 👎.
The staged v0.23 docs, merged at release per the runbook (basic-memory v0.23.0 is live on PyPI/Homebrew):
npm run check:docs+ full Nuxt build pass on the branch.🤖 Generated with Claude Code
https://claude.ai/code/session_01G4rbaeHJN3L7CREp5v38J9