From b9f69e021a2b1eb551928e2d2e0a677b8187e4f9 Mon Sep 17 00:00:00 2001 From: Bregy Malpartida Date: Wed, 30 Sep 2026 14:21:38 -0500 Subject: [PATCH 1/2] chore(cli): pin am integrate to @atomicmemory/mcp-server@0.1.6 --- crates/cli/README.md | 2 +- crates/cli/src/integrate/spec.rs | 2 +- crates/cli/tests/integrate_opencode.rs | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/crates/cli/README.md b/crates/cli/README.md index c70a8de..1f4377f 100644 --- a/crates/cli/README.md +++ b/crates/cli/README.md @@ -325,7 +325,7 @@ am integrate uninstall --host cursor ``` Installs set `ATOMICMEMORY_SCOPE_LOCK=true` in the generated MCP server env and -pin `@atomicmemory/mcp-server@0.1.5`. Project-scoped configs (for example +pin `@atomicmemory/mcp-server@0.1.6`. Project-scoped configs (for example `.cursor/mcp.json` in a repo) are not supported yet — use global install only. OpenCode uses its V2 global `mcp.servers.atomicmemory` configuration under `$XDG_CONFIG_HOME/opencode` or `~/.config/opencode`. diff --git a/crates/cli/src/integrate/spec.rs b/crates/cli/src/integrate/spec.rs index 927e866..1234663 100644 --- a/crates/cli/src/integrate/spec.rs +++ b/crates/cli/src/integrate/spec.rs @@ -21,7 +21,7 @@ use crate::integrate::path_util::require_npx; // "actually resolvable on npm". The build-time test alone does not prove the // pin is published, so a bump belongs in the same release train as the publish // and must not land ahead of it. -pub const MCP_SERVER_PACKAGE: &str = "@atomicmemory/mcp-server@0.1.5"; +pub const MCP_SERVER_PACKAGE: &str = "@atomicmemory/mcp-server@0.1.6"; /// Resolved credentials for writing into host MCP configs. #[derive(Debug, Clone, PartialEq, Eq, Serialize)] diff --git a/crates/cli/tests/integrate_opencode.rs b/crates/cli/tests/integrate_opencode.rs index 033f89c..2fe3175 100644 --- a/crates/cli/tests/integrate_opencode.rs +++ b/crates/cli/tests/integrate_opencode.rs @@ -101,7 +101,7 @@ fn opencode_install_update_doctor_and_uninstall_lifecycle() { assert!( command .iter() - .any(|part| part == "@atomicmemory/mcp-server@0.1.5") + .any(|part| part == "@atomicmemory/mcp-server@0.1.6") ); assert!(command.iter().any(|part| part == "atomicmemory-mcp")); assert_eq!(installed["mcp"]["servers"]["other"]["type"], "remote"); From 294e81d87ca7c001d0ba07ba2d37b93996e64062 Mon Sep 17 00:00:00 2001 From: Bregy Malpartida Date: Wed, 30 Sep 2026 14:23:25 -0500 Subject: [PATCH 2/2] docs(changelog): note am integrate pin bump to mcp-server 0.1.6 --- CHANGELOG.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e26b911..a001805 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -82,9 +82,8 @@ or publish pending. path. The local Core key `local-dev-key` and plain `http://` are refused for Cloud hosts. Plugin manifests and the OpenClaw dependency pin `@atomicmemory/mcp-server@^0.1.6`. Publish `@atomicmemory/mcp-server@0.1.6` - on npm before publishing the 0.2.3 plugins. `am integrate` still pins the - last published `@atomicmemory/mcp-server@0.1.5` until that command's pin is - bumped after the 0.1.6 publish. + on npm before publishing the 0.2.3 plugins. `am integrate` in `am` 0.4.0 pins + `@atomicmemory/mcp-server@0.1.6`. - `@atomicmemory/cli` (`atomicmemory`) is **deprecated** in favor of `am`; see consolidation doc for command mapping and smoke-contract updates. It stays published and supported for `import --type llmwiki` (not yet ported to `am`