nexusmem 0.10.1 → 0.10.3

package/CHANGELOG.md

@@ -11,6 +11,38 @@ built from, matched by publish timestamp: `v0.1.0` → `67a4776`, `v0.1.1` → `
 
 No unreleased changes yet.
 
+## [0.10.3] — 2026-08-31
+
+### Added
+
+- `hook git-post install|remove|status`: an opt-in git post-commit hook that runs a full
+  `nexusmem sync` (including embedding) in the background after every commit. Detached (`nohup ... &`),
+  so it never makes `git commit` itself wait; output goes to `.nexusmem/post-commit-sync.log` instead
+  of the terminal. `sync` gained a matching `--auto` flag (used only by this hook) that skips instead
+  of running if another `--auto` sync already holds an advisory lock over the project's workspace dir —
+  a burst of commits (e.g. a rebase) coalesces into one sync instead of piling up. The log file is
+  reset once it passes 2000 lines so it can't grow forever, and a skipped/coalesced run is always
+  reported there, even though the hook always passes `--quiet`.
+
+### Known limitations
+
+- A burst of commits fast enough to launch genuinely overlapping `sync --auto` processes can
+  interleave two runs' text mid-line in `.nexusmem/post-commit-sync.log` — the advisory lock
+  serializes the actual database writes (never at risk), not who gets to write to this diagnostic
+  log file. Cosmetic only; not planned to be fixed unless it turns out to matter in practice.
+
+## [0.10.2] — 2026-08-30
+
+### Security
+
+- `shell_command` nodes never ran through the same secret-redaction pass `conversation_turn` and
+  `code_diff` nodes already get: a command like `export API_KEY=...` landed verbatim in `title`/`body`,
+  which is exactly what the FTS index and vector embeddings are built from — a secret typed at a
+  prompt could resurface later through `search_memory`/`nexusmem query`. Fixed by running `redact()`
+  over the command before it reaches those fields. `meta.command` is kept raw on purpose: project-id
+  reconciliation and failure/fix correlation both hash or exact-match against the real command text,
+  and redacting that copy too would have silently orphaned nodes on a project-id migration.
+
 ## [0.10.1] — 2026-08-30
 
 ### Added