@syncular/server-workers 0.15.45 → 0.15.47

package/README.md

@@ -113,7 +113,9 @@ wrangler d1 migrations apply syncular
 
 The schema is plain SQLite DDL (shared with `bun:sqlite` via
 `sqlite-dialect.ts`), so it is portable across the two SQLite-family
-storages.
+storages. Regenerate and apply a migration when upgrading Syncular adds a core
+table. The durable reaction queue uses `sync_reactions`; a Worker running a
+reaction planner or runner fails closed if that migration is absent.
 
 ## Storage: D1 (`D1ServerStorage`)
 
@@ -129,6 +131,19 @@ immediately (autocommit) and **buffers** writes, flushing them as one atomic
 rolls back by never flushing). A read-your-own-writes overlay makes `getRow`
 see buffered writes of the same commit.
 
+Durable reactions use the same model. Planned rows join the source commit's
+atomic batch. `ReactionRunner` claims due rows with one
+`UPDATE ... RETURNING` statement, so concurrent Workers have no select/update
+gap. Reaction handlers execute outside the source transaction. Run the runner
+from a Worker scheduler, queue consumer, Workflow step, or Durable Object
+alarm according to the application's hosting model.
+
+Schedule `pruneReactions` per partition as a separate maintenance pass.
+Defaults retain completed rows for 30 days and dead-lettered rows for 90 days,
+with at most 1,000 deletions per pass. Repeat while `mayHaveMore` is true.
+Pending and leased rows are never eligible. D1 executes each bounded cleanup
+as one `DELETE ... RETURNING` statement.
+
 **Concurrency posture.** Every push, not only whole-commit validation, must
 serialize before operation reads and re-check idempotency under that boundary.
 `createWorkersFetchHandler` forwards `/sync` to one DO per authenticated
@@ -316,9 +331,10 @@ WRANGLER_SMOKE=1`-gated test wrapping exactly this recipe.
 The server core this entry loads (handler, realtime session, D1 storage,
 memory stores, signed-URL/segment/blob machinery) is free of Bun- and
 Node-only builtins — SigV4 and all hashing use Web Crypto, base64 uses
-`btoa`/`atob`, and the SQLite-family stores that need `bun:sqlite`
+`btoa`/`atob`, and the SQLite-family stores that need `bun:sqlite` or
+`node:sqlite`
 (`SqliteServerStorage`, `SqliteSegmentStore`, `SqliteBlobStore`,
 `SqliteLeaseStore`, `buildSqliteImage`) live in separate modules a Bun/Node
-host opts into and a Workers bundle tree-shakes away. This is enforced by a
+host imports through `@syncular/server/sqlite`. This is enforced by a
 static import-graph scan in
 `packages/server/test/runtime-neutrality.test.ts`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@syncular/server-workers",
-  "version": "0.15.45",
+  "version": "0.15.47",
   "description": "Cloudflare Workers adapter for the Syncular sync server",
   "license": "Apache-2.0",
   "author": "Benjamin Kniffler",
@@ -45,10 +45,10 @@
     "!dist/**/*.test.d.ts"
   ],
   "dependencies": {
-    "@syncular/server": "0.15.45",
-    "@syncular/server-hono": "0.15.45"
+    "@syncular/server": "0.15.47",
+    "@syncular/server-hono": "0.15.47"
   },
   "devDependencies": {
-    "@syncular/core": "0.15.45"
+    "@syncular/core": "0.15.47"
   }
 }