@uns-kit/core 3.0.12 → 3.0.14
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/MIGRATIONS.md +18 -0
- package/package.json +1 -1
package/MIGRATIONS.md
CHANGED
|
@@ -9,6 +9,24 @@ Agents must inspect the application's existing ownership and shutdown flow
|
|
|
9
9
|
before editing it. The examples below describe the intended behavior, not a
|
|
10
10
|
mechanical search-and-replace operation.
|
|
11
11
|
|
|
12
|
+
## 3.0.13 - Optional controller-correlated handovers
|
|
13
|
+
|
|
14
|
+
`UnsProxyProcess` accepts an optional `handoverId` parameter or
|
|
15
|
+
`UNS_HANDOVER_ID` environment variable. When supplied, it adds that opaque id
|
|
16
|
+
to handover MQTT payloads and MQTT 5 user properties. A new target includes
|
|
17
|
+
the id in its final `handover_ack`, even when its source still runs an older
|
|
18
|
+
uns-kit that does not echo the id.
|
|
19
|
+
|
|
20
|
+
Existing applications need no configuration or source change: without this
|
|
21
|
+
value their MQTT messages remain byte-for-byte compatible with the legacy
|
|
22
|
+
handover protocol. To opt an RTT target into controller-coordinated hot
|
|
23
|
+
migration, set `uns.handoverProtocol: "correlated-v1"` alongside
|
|
24
|
+
`uns.instanceMode: "handover"` and `uns.handover: true`. A controller should
|
|
25
|
+
inject the value only for a durable, operator-initiated migration and must
|
|
26
|
+
still accept an acknowledgement without the id from a legacy target. The value
|
|
27
|
+
is correlation metadata, not a secret; do not use it as an authorization or
|
|
28
|
+
fencing token.
|
|
29
|
+
|
|
12
30
|
## 3.0.12 - Expiring retained handover heartbeats
|
|
13
31
|
|
|
14
32
|
`UnsProxyProcess` now publishes its `active` heartbeat as an MQTT 5 retained
|