traqr-memory-mcp 0.2.11 → 0.2.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/UPGRADING.md +33 -0
- package/package.json +1 -1
package/UPGRADING.md
CHANGED
|
@@ -26,6 +26,39 @@
|
|
|
26
26
|
|
|
27
27
|
4. Restart the MCP server. The startup line should now show the new schema version.
|
|
28
28
|
|
|
29
|
+
## Gotcha: the `npx` cache can freeze you at a stale version
|
|
30
|
+
|
|
31
|
+
Most MCP clients launch this server via **`npx -y traqr-memory-mcp`** (see your
|
|
32
|
+
client config, e.g. `~/.claude.json` → `mcpServers`), **not** via a local
|
|
33
|
+
`npm install`. That changes how upgrades take effect:
|
|
34
|
+
|
|
35
|
+
- With an **unpinned** spec (`traqr-memory-mcp`, no `@version`), npx resolves the
|
|
36
|
+
dependency tree **once**, caches it under `~/.npm/_npx/<hash>/node_modules/`,
|
|
37
|
+
and on later spawns **reuses the cache without re-checking the registry**. New
|
|
38
|
+
publishes never load — you can run week-old code while believing your merges
|
|
39
|
+
and `npm update` took effect. (This bit the whole Traqr fleet 2026-06-07 →
|
|
40
|
+
06-14: ~7-day-stale memory code ran fleet-wide while every published fix sat
|
|
41
|
+
unloaded. See `docs/claude/proxy-invariant.md` § Distribution layer.)
|
|
42
|
+
|
|
43
|
+
**`npm update` does NOT fix this** — it updates a local `node_modules`, but the
|
|
44
|
+
npx launcher reads from the separate `_npx` cache.
|
|
45
|
+
|
|
46
|
+
**Fixes (either works):**
|
|
47
|
+
|
|
48
|
+
1. **Clear the npx cache** so the next spawn re-resolves to the latest publish:
|
|
49
|
+
```bash
|
|
50
|
+
rm -rf ~/.npm/_npx/* # or just the specific <hash> dir holding it
|
|
51
|
+
```
|
|
52
|
+
2. **Pin `@latest` in your MCP config** so npx re-checks the registry every
|
|
53
|
+
spawn (no freeze, at the cost of one registry round-trip per cold start):
|
|
54
|
+
```jsonc
|
|
55
|
+
"args": ["-y", "traqr-memory-mcp@latest"]
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
**Either way, restart your MCP client.** An already-running server keeps the
|
|
59
|
+
stale code in memory until the client session (e.g. Claude Code) restarts — a
|
|
60
|
+
cache clear only takes effect on the next process spawn.
|
|
61
|
+
|
|
29
62
|
## Schema Version Policy
|
|
30
63
|
|
|
31
64
|
- **Patch updates** (0.1.x) never change the database schema
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "traqr-memory-mcp",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.12",
|
|
4
4
|
"description": "Memory-as-a-service MCP server for AI agents. 11 tools, Postgres + pgvector, multi-strategy retrieval. Works with Claude Code, Cursor, Codex, and any MCP client.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|