schplitt · schplitt · Jul 30, 2026 · Jul 30, 2026
diff --git a/.changeset/kernel-async-context.md b/.changeset/kernel-async-context.md
diff --git a/.changeset/ninety-parrots-act.md b/.changeset/ninety-parrots-act.md
diff --git a/.changeset/silent-otters-jump.md b/.changeset/silent-otters-jump.md
diff --git a/.changeset/tidy-errors-passthrough.md b/.changeset/tidy-errors-passthrough.md
diff --git a/packages/durable-isolates/CHANGELOG.md b/packages/durable-isolates/CHANGELOG.md
@@ -0,0 +1,13 @@
+# durable-isolates
+
+## 0.1.0
+
+### Minor Changes
+
+- de4f12d: feat: async-context boundary prefix (parallel-safe nesting), split bridge globals, reserved-specifier guard
+
+### Patch Changes
+
+- 43fbd92: feat: durable isolates
+- 5827d5f: chore: bump `@iso4/sandbox` to `^0.4.0`
+- 7ce225a: Faithful durable-call error propagation on iso4 >=0.2.2. A failed durable call now REJECTS the bridge with the recorded error instead of returning an `{ ok: false }` envelope: iso4 (>=0.2.2, which closed schplitt/iso4#22) delivers a rejecting bridge into the sandbox `catch` as a real `Error` with its `name`/`message`/own fields intact, and surfaces a structured `RunError` (`name`/`message`/`fields`) on the host for uncaught failures. This removes the hand-rolled `serializeError`/`__di_reconstruct` workaround and the exported `SerializedError` type — `FailedResult.error` and `FailedBoundary.error` are now `unknown` (the thrown value recorded as plain, persistable data, with the host `stack` stripped). Bumps the `@iso4/sandbox` floor to `^0.2.2`.
diff --git a/packages/durable-isolates/package.json b/packages/durable-isolates/package.json
@@ -1,6 +1,6 @@
 {
   "name": "durable-isolates",
-  "version": "0.0.0",
+  "version": "0.1.0",
   "type": "module",
   "description": "The replay kernel for durable-workflows: durably execute one isolate program over a log, built on top of iso4",
   "keywords": [