@fabricorg/webhook-delivery 0.1.1 → 0.1.3

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # @fabricorg/webhook-delivery
 
+## 0.1.3
+
+### Patch Changes
+
+- 8d87a36: Accept `@fabricorg/platform-host` 8 as a peer. Host 8 changes the meaning of some failure statuses but no API these packages use, so they work with 7 and 8 unchanged.
+- 939bcad: Build packages with tsdown in place of tsup. Preserve the published ESM/CommonJS
+  entry paths, ES2022 target, declaration filenames, and raw external module
+  specifier spellings, including the existing Node built-in spellings.
+
+  Generated JavaScript, source-map contents, declaration formatting, and internal
+  chunk layout change. Comparison with the saved tsup build found unchanged named
+  runtime exports and public declaration signatures. Declaration maps remain
+  unpublished. Facade maps are no longer published for Platform's root, evidence,
+  and policies entries, or experience-runtime's contracts entry (both `.js.map`
+  and `.cjs.map`). Their new JavaScript output has no source-map URL comment.
+
+  CommonJS interop: 29 of 72 baseline CJS files expose an `__esModule` marker;
+  0 of 57 tsdown CJS files do. The compared package entries have no default runtime
+  export, and the emitted `.d.cts` files declare none. Typed consumers of the
+  unchanged declared exports are unaffected. For entries whose marker was removed,
+  an untyped CJS `import X from` compiled with a Babel-style default-interop helper
+  now yields the namespace instead of `undefined`.
+
+## 0.1.2
+
+### Patch Changes
+
+- 5d93521: Republish workspace dependents of `@fabricorg/platform` and `@fabricorg/platform-host`, including transitive and development dependencies, alongside the handler reconciliation contract (issue #70). Workspace ranges resolve to the released versions when packed; existing literal compatibility ranges remain unchanged. Runtime source is unchanged. Private example workspaces are not published.
+
 ## 0.1.1
 
 ### Patch Changes

package/README.md

@@ -388,10 +388,16 @@ before the clock is read or anything is written. It also runs at `written`, afte
 before the commit. A call that returns a refusal does not reach `written`. Leave both unset
 outside tests.
 
-**Running the live suite.** Run `FABRIC_POSTGRES_TEST_URL=postgresql://… pnpm exec vitest run
-tests/postgres-live.test.ts` in this package, or `pnpm test:postgres` at the root, which the
-`postgres-certification` CI job runs. Without the variable the suite is skipped. It creates one
-database per run and one schema per store pair.
+**Running the live suite.** From the repository root, run `pnpm build`, then
+`pnpm test:postgres`. The runner starts a throwaway `postgres:16` database on a free localhost
+port and removes it in its cleanup block after success, failure, Ctrl-C, or SIGTERM. Docker
+must be installed and usable. `FABRIC_POSTGRES_TEST_IMAGE` overrides the image, and
+`FABRIC_POSTGRES_TEST_TIMEOUT_SECONDS` overrides the 60-second readiness timeout. An existing
+`FABRIC_POSTGRES_TEST_URL` bypasses Docker and is passed unchanged, as in the
+`postgres-certification` CI job. The runner reports missing builds with `Run pnpm build first`;
+rebuild after source changes. See the Live certification section in the repository file
+`docs/operations/releasing.md` for cleanup limits and runner tests. Direct Vitest runs skip this file without the URL.
+The suite creates one database per run and one schema per store pair.
 
 ### Contract suite