omo-memory 0.1.16 → 0.1.17
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/README.md +1 -1
- package/dist/autoUpdate.js +2 -1
- package/docs/adapter-integration.md +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -136,7 +136,7 @@ Initial stdio MCP tools:
|
|
|
136
136
|
|
|
137
137
|
## Updates
|
|
138
138
|
|
|
139
|
-
Installed CLI commands automatically launch a quiet background `npm install -g omo-memory@latest` at most once per day. MCP startup does not run the updater, so stdio handshakes stay clean. The package `postinstall` cleanup also runs during these updates and removes legacy Codex `omo-memory@islee23520` hook registrations.
|
|
139
|
+
Installed CLI commands automatically launch a quiet background `npm install -g --allow-scripts=omo-memory,better-sqlite3 omo-memory@latest` at most once per day. MCP startup does not run the updater, so stdio handshakes stay clean. The package `postinstall` cleanup also runs during these updates and removes legacy Codex `omo-memory@islee23520` hook registrations.
|
|
140
140
|
|
|
141
141
|
Manual update:
|
|
142
142
|
|
package/dist/autoUpdate.js
CHANGED
|
@@ -3,6 +3,7 @@ import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
|
|
|
3
3
|
import { homedir } from "node:os";
|
|
4
4
|
import { dirname, join } from "node:path";
|
|
5
5
|
const PACKAGE_NAME = "omo-memory";
|
|
6
|
+
const ALLOWED_INSTALL_SCRIPTS = "omo-memory,better-sqlite3";
|
|
6
7
|
const DEFAULT_INTERVAL_MS = 86_400_000;
|
|
7
8
|
const STATE_PATH = join(homedir(), ".omo", "memory", "auto-update.json");
|
|
8
9
|
export function maybeRunAutoUpdate(currentVersion, nowMs = Date.now()) {
|
|
@@ -74,7 +75,7 @@ function npmCommand() {
|
|
|
74
75
|
}
|
|
75
76
|
function installArgs() {
|
|
76
77
|
const target = process.env["OMO_MEMORY_UPDATE_TARGET"] ?? `${PACKAGE_NAME}@latest`;
|
|
77
|
-
return ["install", "-g", target];
|
|
78
|
+
return ["install", "-g", `--allow-scripts=${ALLOWED_INSTALL_SCRIPTS}`, target];
|
|
78
79
|
}
|
|
79
80
|
function updateEnv(currentVersion) {
|
|
80
81
|
return { ...process.env, OMO_MEMORY_AUTO_UPDATE_CHILD: "1", OMO_MEMORY_CURRENT_VERSION: currentVersion };
|
|
@@ -144,7 +144,7 @@ Use these tools:
|
|
|
144
144
|
- `memory_global_list`
|
|
145
145
|
|
|
146
146
|
|
|
147
|
-
CLI updates: normal CLI commands automatically launch a quiet background `npm install -g omo-memory@latest` at most once per day. MCP startup intentionally does not auto-update because stdout/stderr must remain reserved for the protocol. Hosts that need pinned installs should set `OMO_MEMORY_AUTO_UPDATE=0` in the CLI environment. Package install/update also runs the Codex stale-hook cleanup migration through `postinstall`.
|
|
147
|
+
CLI updates: normal CLI commands automatically launch a quiet background `npm install -g --allow-scripts=omo-memory,better-sqlite3 omo-memory@latest` at most once per day. MCP startup intentionally does not auto-update because stdout/stderr must remain reserved for the protocol. Hosts that need pinned installs should set `OMO_MEMORY_AUTO_UPDATE=0` in the CLI environment. Package install/update also runs the Codex stale-hook cleanup migration through `postinstall`.
|
|
148
148
|
|
|
149
149
|
Global migration is copy/import only. Adapters may scan for existing project-local `.omo/memory/state.sqlite` databases and import their event/session/handoff ledgers into a user-selected global SQLite file, but they must preserve source DBs and retain source provenance in the global store.
|
|
150
150
|
|