@uns-kit/cli 3.0.34 → 3.0.35

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@uns-kit/cli",
3
- "version": "3.0.34",
3
+ "version": "3.0.35",
4
4
  "description": "Command line scaffolding tool for UNS applications",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -26,14 +26,14 @@
26
26
  ],
27
27
  "dependencies": {
28
28
  "azure-devops-node-api": "^15.1.2",
29
- "@uns-kit/core": "3.0.34"
29
+ "@uns-kit/core": "3.0.35"
30
30
  },
31
31
  "unsKitPackages": {
32
- "@uns-kit/core": "3.0.34",
33
- "@uns-kit/api": "3.0.34",
34
- "@uns-kit/cron": "3.0.34",
35
- "@uns-kit/database": "3.0.34",
36
- "@uns-kit/assistant-workflow": "3.0.34"
32
+ "@uns-kit/core": "3.0.35",
33
+ "@uns-kit/api": "3.0.35",
34
+ "@uns-kit/cron": "3.0.35",
35
+ "@uns-kit/database": "3.0.35",
36
+ "@uns-kit/assistant-workflow": "3.0.35"
37
37
  },
38
38
  "scripts": {
39
39
  "build": "tsc -p tsconfig.build.json",
@@ -31,6 +31,7 @@ Pointers for AI/code-assist tools when working in this generated project.
31
31
  - When crossing `<3.0.29` to `>=3.0.29`, configuration-owned process groups opt into shared protocol2/policy4. Keep business resources in the app, bind immutable snapshots and journal generations, use reviewed generation/version transitions, and preserve old journals/policies. Ordinary services and existing file groups need no migration.
32
32
 
33
33
  - Before changing any `@uns-kit/*` version, record the installed source version and intended target version.
34
+ - When opting into SDK 3.0.35 state-preserving MQTT handover, declare protocol2 and per-proxy semantic contracts. Never infer compatibility from package version or matching paths. Use a reviewed reverse handover for return ownership; a cold restart cannot recover counter baselines from RAM. See the version-bounded migration and SDK example.
34
35
  - After installing the target version, read `node_modules/@uns-kit/core/MIGRATIONS.md` and apply every migration whose version boundary is crossed. Do not apply unrelated migrations.
35
36
  - When crossing `<2.0.71` to `>=2.0.71`, inspect MQTT proxy ownership and follow the documented shutdown migration. Process-owned and standalone proxies have different shutdown paths.
36
37
  - When crossing `<3.0.0` to `>=3.0.0`, migrate MQTT `message.table.columns` publishers from named arrays to named objects and consumers to object-entry iteration. Keep schema `tableColumns` and Assistant/UI table formats unchanged.