@fabricorg/platform-host 7.2.1 → 7.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +6 -0
- package/MIGRATION-7.md +34 -0
- package/package.json +4 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# @fabricorg/platform-host
|
|
2
2
|
|
|
3
|
+
## 7.2.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 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.
|
|
8
|
+
|
|
3
9
|
## 7.2.1
|
|
4
10
|
|
|
5
11
|
### Patch Changes
|
package/MIGRATION-7.md
ADDED
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
# Migrating to @fabricorg/platform-host 7
|
|
2
|
+
|
|
3
|
+
**Nothing in your code has to change.** Version 7.0.0 carries no source change
|
|
4
|
+
of its own. Its only entry is a dependency update: `@fabricorg/assembly` went
|
|
5
|
+
to 0.4.0, and a peer range on a pre-1.0 package moved, which forces a major
|
|
6
|
+
here even though this package's behaviour and public surface are identical to
|
|
7
|
+
6.x.
|
|
8
|
+
|
|
9
|
+
This document exists because the support policy says a major carries one. A
|
|
10
|
+
major with nothing to migrate should say so plainly rather than leave you
|
|
11
|
+
reading a changelog to find out.
|
|
12
|
+
|
|
13
|
+
## What to check anyway
|
|
14
|
+
|
|
15
|
+
Upgrade `@fabricorg/assembly` alongside it. The supported set is pinned in
|
|
16
|
+
`contracts/fabric-family/compatibility.v1.json`; mixing versions across the
|
|
17
|
+
family may work and is not supported.
|
|
18
|
+
|
|
19
|
+
## What actually changed after 7.0.0
|
|
20
|
+
|
|
21
|
+
The releases that follow it do carry behaviour, and are worth reading if you
|
|
22
|
+
are coming from 6.x:
|
|
23
|
+
|
|
24
|
+
- **7.1.0** — the host reads an action's `completion` mode. An adapter that
|
|
25
|
+
returns `acceptedExternalOperation` parks the invocation with a durable
|
|
26
|
+
handoff; `completeExternalInvocation` settles it by external reference;
|
|
27
|
+
`reconcileOverdueCompletions` sweeps handoffs past their deadline. A custom
|
|
28
|
+
store must persist `pendingCompletion` and `externalCompletion`, or the
|
|
29
|
+
worker re-runs a handoff. PostgreSQL migration 3 adds the columns.
|
|
30
|
+
- **7.1.1** — a repeated completion is judged by a content digest, so a second
|
|
31
|
+
callback carrying a different result is a contradiction rather than an
|
|
32
|
+
absorbed replay.
|
|
33
|
+
- **7.2.0** — `tenantIsolationChecks()`, six checks proving scope is a key on
|
|
34
|
+
every read, write, claim, and completion. Run them against your store.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@fabricorg/platform-host",
|
|
3
|
-
"version": "7.2.
|
|
3
|
+
"version": "7.2.2",
|
|
4
4
|
"description": "Canonical governed mutation host for @fabricorg/platform: durable invocation, policy, state-machine, handler, event, and adapter orchestration behind persistence ports.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"fabric",
|
|
@@ -41,6 +41,7 @@
|
|
|
41
41
|
"README.md",
|
|
42
42
|
"MIGRATION-2-IDEMPOTENCY.md",
|
|
43
43
|
"MIGRATION-6-PRODUCTION.md",
|
|
44
|
+
"MIGRATION-7.md",
|
|
44
45
|
"CHANGELOG.md",
|
|
45
46
|
"LICENSE"
|
|
46
47
|
],
|
|
@@ -53,8 +54,8 @@
|
|
|
53
54
|
"tsup": "^8.5.0",
|
|
54
55
|
"typescript": "^5.7.3",
|
|
55
56
|
"vitest": "^4.1.5",
|
|
56
|
-
"@fabricorg/
|
|
57
|
-
"@fabricorg/
|
|
57
|
+
"@fabricorg/assembly": "^0.4.2",
|
|
58
|
+
"@fabricorg/platform": "1.5.1"
|
|
58
59
|
},
|
|
59
60
|
"engines": {
|
|
60
61
|
"node": ">=20"
|