Conversation
Two community contributions on top of 0.8.3 land as a patch release so they reach users immediately and so `npx agentmemory-mcp` ships to the npm registry for the first time (closing out #120 on the live release). - #122 (Jason Landbridge): memory_save persists to disk immediately after every call, not just on SIGINT/SIGTERM, so memories survive SIGKILL from agent sessions ending forcefully - #121 (Jason Landbridge): OpenCode MCP config format corrected — opencode.json with mcp/type:local/command array instead of the wrong .opencode/config.json with mcpServers Version bumped across package.json, src/version.ts, types.ts, export-import supportedVersions, plugin.json, shim package.json and its dependency on the main package (~0.8.4). package-lock.json regenerated. 684 tests passing, clean build.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (8)
📝 WalkthroughWalkthroughVersion bump from 0.8.3 to 0.8.4 across all package manifests, version constants, and type definitions. Updates include documentation of fixes for standalone MCP memory persistence and OpenCode MCP configuration instructions. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Cuts v0.8.4 as a patch release bundling two community contributions that landed on top of v0.8.3 (#123) but haven't shipped to the registry yet.
What's in this release
memory_saveSIGKILL data loss (thanks @JasonLandbridge). The standalone MCP server only flushed to~/.agentmemory/standalone.jsononSIGINT/SIGTERM. Anymemory_saveduring an agent session that got SIGKILL'd (OpenCode session end, parent process crash) was lost. Now persists on every save..opencode/config.jsonwithmcpServers, but OpenCode actually usesopencode.jsonwithmcp/type: "local"/commandarray. Fixed in the agents table and a new dedicated OpenCode block in the Standalone MCP section.Why cut this now
v0.8.3 fixed issue #120 (the
npx agentmemory-mcp404) structurally — published a shim package + canonical CLI subcommand — but the publish hasn't run yet because #123 merged after the last release cut. Cutting 0.8.4 lets the publish workflow fire, push both@agentmemory/agentmemory@0.8.4andagentmemory-mcp@0.8.4to npm for the first time, and verify the shim actually installs. At that point #120 is closed both structurally and on the live registry.The SIGKILL fix is also real data-loss worth shipping immediately rather than bundling into the next feature release.
Changes
src/version.ts,src/types.ts(ExportData union),src/functions/export-import.ts(supportedVersions),test/export-import.test.ts— version bumped to 0.8.4package.json,package-lock.json,plugin/.claude-plugin/plugin.json— version bumpedpackages/agentmemory-mcp/package.json— version bumped + dep pinned to~0.8.4CHANGELOG.md— new 0.8.4 entry crediting Jason for both PRs + reference link targetTest plan
npm test→ 684 / 684 passingnpm run build→ cleanv0.8.4to trigger the publish workflownpm view @agentmemory/agentmemory@0.8.4+npm view agentmemory-mcp@0.8.4/tmpdir:npx agentmemory-mcpshould boot the standalone MCP server without 404 (the whole point of MCP Install Failed #120)Summary by CodeRabbit