@cerefox/memory 0.8.2 → 0.8.3

package/dist/bin/cerefox.js

@@ -7184,7 +7184,7 @@ var exports_meta = {};
 __export(exports_meta, {
   PKG_VERSION: () => PKG_VERSION
 });
-var PKG_VERSION = "0.8.2";
+var PKG_VERSION = "0.8.3";
 var init_meta = () => {};
 
 // ../../node_modules/.bun/tslib@2.8.1/node_modules/tslib/tslib.js

package/docs/guides/setup-supabase.md

@@ -221,9 +221,17 @@ Deployed Functions on project <your-project-ref>: cerefox-ingest
 You can verify in the Supabase Dashboard → **Edge Functions** — all three functions should
 appear with a green "Active" status.
 
+> **`WARNING: Docker is not running` is expected and harmless.** The Supabase CLI checks for
+> Docker (its older local bundler ran in a container) but falls back to bundling the functions
+> server-side — it uploads the source assets (you'll see `Uploading asset (…)` lines) and
+> Supabase compiles them in the cloud. **Docker is not a prerequisite for deploying Cerefox's
+> Edge Functions.** A deploy succeeded as long as each function ends with
+> `Deployed Functions on project …`. This applies to both the manual commands here and
+> `cerefox deploy-server --functions-only`.
+
 > **Re-deploying after updates**: run the same `npx supabase functions deploy` commands
-> again from the project root. `npx supabase login` and `npx supabase link` only need to be
-> run once per machine.
+> again from the project root, or just `cerefox deploy-server --functions-only` (it deploys
+> all 9 from the bundled assets). `npx supabase login` only needs to be run once per machine.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cerefox/memory",
-  "version": "0.8.2",
+  "version": "0.8.3",
   "description": "Cerefox — user-owned shared memory for AI agents. The local TypeScript runtime: stdio MCP server in v0.4; CLI binary added in v0.5; in-process web server in v0.6; ingestion pipeline in v0.7.",
   "license": "Apache-2.0",
   "homepage": "https://github.com/fstamatelopoulos/cerefox",