@cerefox/memory 1.9.1 → 1.10.0
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/dist/bin/cerefox.js +264 -92
- package/dist/frontend/assets/index-i67RH1VY.js +121 -0
- package/dist/frontend/assets/index-i67RH1VY.js.map +1 -0
- package/dist/frontend/index.html +1 -1
- package/dist/server-assets/_shared/ef-meta/index.ts +3 -3
- package/dist/server-assets/_shared/mcp-tools/_document-meta.ts +377 -0
- package/dist/server-assets/_shared/mcp-tools/_projects.ts +13 -32
- package/dist/server-assets/_shared/mcp-tools/_utils.ts +9 -2
- package/dist/server-assets/_shared/mcp-tools/types.ts +6 -2
- package/dist/server-assets/db/migrations/0030_rename_document_rpc.sql +80 -0
- package/dist/server-assets/db/rpcs.sql +63 -1
- package/dist/server-assets/db/schema.sql +1 -1
- package/docs/guides/upgrading.md +16 -3
- package/package.json +1 -1
- package/dist/frontend/assets/index-DWT7wZMR.js +0 -121
- package/dist/frontend/assets/index-DWT7wZMR.js.map +0 -1
package/docs/guides/upgrading.md
CHANGED
|
@@ -1,8 +1,21 @@
|
|
|
1
1
|
# Upgrading Cerefox
|
|
2
2
|
|
|
3
|
-
Upgrading is almost always
|
|
4
|
-
server side if the release changed it
|
|
5
|
-
to re-run.
|
|
3
|
+
Upgrading is almost always three steps, **in this order**: update the CLI,
|
|
4
|
+
re-deploy the server side if the release changed it, then re-sync the bundled
|
|
5
|
+
guides. Everything here is idempotent and safe to re-run.
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
cerefox self-update # 1. the client
|
|
9
|
+
cerefox server deploy # 2. schema + RPCs + Edge Functions (if the release changed them)
|
|
10
|
+
cerefox guides ingest # 3. the bundled guides, into your KB
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
The order matters: a release may require its own schema (the version notes
|
|
14
|
+
say so — v1.9.x is one), and until `server deploy` runs, the freshly updated
|
|
15
|
+
client is talking to the previous release's server. That is why
|
|
16
|
+
`self-update` no longer runs the guides sync automatically — it used to fire
|
|
17
|
+
at the one moment in the upgrade where it cannot succeed against a
|
|
18
|
+
schema-requiring release.
|
|
6
19
|
|
|
7
20
|
## Pick your path
|
|
8
21
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cerefox/memory",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.10.0",
|
|
4
4
|
"description": "Cerefox — user-owned shared memory for AI agents. CLI + stdio MCP server + web UI + ingestion for a knowledge base on your own Supabase project (or fully self-hosted with Cerefox Local).",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"homepage": "https://github.com/fstamatelopoulos/cerefox",
|