@fabricorg/platform-host 7.2.0 → 7.2.2

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @fabricorg/platform-host
 
+## 7.2.2
+
+### Patch Changes
+
+- 796b9d5: Ship `MIGRATION-7.md`. Version 7.0.0 carried no source change of its own, only a peer range that moved, and the support policy promises every major carries a migration document. The document says exactly that, and points at what 7.1 and 7.2 did change.
+
+## 7.2.1
+
+### Patch Changes
+
+- 1b81b20: Publish with real build provenance, and name the repository each attestation points at. `pnpm publish` accepts `--provenance` and drops it, so every release until now was unattested while the release document claimed otherwise. The pipeline now packs with pnpm and uploads the tarball with `npm publish --provenance`, and every package declares `repository`, `homepage`, and `bugs`.
+
 ## 7.2.0
 
 ### Minor Changes

package/MIGRATION-7.md

@@ -0,0 +1,34 @@
+# Migrating to @fabricorg/platform-host 7
+
+**Nothing in your code has to change.** Version 7.0.0 carries no source change
+of its own. Its only entry is a dependency update: `@fabricorg/assembly` went
+to 0.4.0, and a peer range on a pre-1.0 package moved, which forces a major
+here even though this package's behaviour and public surface are identical to
+6.x.
+
+This document exists because the support policy says a major carries one. A
+major with nothing to migrate should say so plainly rather than leave you
+reading a changelog to find out.
+
+## What to check anyway
+
+Upgrade `@fabricorg/assembly` alongside it. The supported set is pinned in
+`contracts/fabric-family/compatibility.v1.json`; mixing versions across the
+family may work and is not supported.
+
+## What actually changed after 7.0.0
+
+The releases that follow it do carry behaviour, and are worth reading if you
+are coming from 6.x:
+
+- **7.1.0** — the host reads an action's `completion` mode. An adapter that
+  returns `acceptedExternalOperation` parks the invocation with a durable
+  handoff; `completeExternalInvocation` settles it by external reference;
+  `reconcileOverdueCompletions` sweeps handoffs past their deadline. A custom
+  store must persist `pendingCompletion` and `externalCompletion`, or the
+  worker re-runs a handoff. PostgreSQL migration 3 adds the columns.
+- **7.1.1** — a repeated completion is judged by a content digest, so a second
+  callback carrying a different result is a contradiction rather than an
+  absorbed replay.
+- **7.2.0** — `tenantIsolationChecks()`, six checks proving scope is a key on
+  every read, write, claim, and completion. Run them against your store.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fabricorg/platform-host",
-  "version": "7.2.0",
+  "version": "7.2.2",
   "description": "Canonical governed mutation host for @fabricorg/platform: durable invocation, policy, state-machine, handler, event, and adapter orchestration behind persistence ports.",
   "keywords": [
     "fabric",
@@ -13,7 +13,7 @@
   "author": "Fabric",
   "repository": {
     "type": "git",
-    "url": "https://github.com/Fabric-Pro/fabric-platform.git",
+    "url": "git+https://github.com/Fabric-Pro/fabric-platform.git",
     "directory": "packages/platform-host"
   },
   "homepage": "https://github.com/Fabric-Pro/fabric-platform/tree/main/packages/platform-host#readme",
@@ -41,6 +41,7 @@
     "README.md",
     "MIGRATION-2-IDEMPOTENCY.md",
     "MIGRATION-6-PRODUCTION.md",
+    "MIGRATION-7.md",
     "CHANGELOG.md",
     "LICENSE"
   ],
@@ -53,8 +54,8 @@
     "tsup": "^8.5.0",
     "typescript": "^5.7.3",
     "vitest": "^4.1.5",
-    "@fabricorg/platform": "1.5.0",
-    "@fabricorg/assembly": "^0.4.1"
+    "@fabricorg/assembly": "^0.4.2",
+    "@fabricorg/platform": "1.5.1"
   },
   "engines": {
     "node": ">=20"