@uns-kit/cli 3.0.21 → 3.0.23

package/dist/index.js

@@ -526,6 +526,7 @@ const AGENT_MIGRATION_BLOCK = [
     "## UNS Kit dependency upgrades",
     "",
     "- Before changing any `@uns-kit/*` version, record the installed source version and intended target version.",
+    "- When crossing `<3.0.23` to `>=3.0.23`, applications with accepted work outside MQTT should register `handoverShutdown` before creating proxies; its async drain must not call `process.exit`.",
     "- 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.",
     "- 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.",
     "- 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.",

package/dist/service-bundle.js

@@ -79,6 +79,7 @@ export function generateAgentsMarkdown(bundle) {
         "## UNS Kit dependency upgrades",
         "",
         "- Before changing any `@uns-kit/*` version, record the installed source version and intended target version.",
+        "- When crossing `<3.0.23` to `>=3.0.23`, applications with accepted work outside MQTT should register `handoverShutdown` before creating proxies; its async drain must not call `process.exit`.",
         "- 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.",
         "- 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.",
         "- 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.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uns-kit/cli",
-  "version": "3.0.21",
+  "version": "3.0.23",
   "description": "Command line scaffolding tool for UNS applications",
   "type": "module",
   "license": "MIT",
@@ -26,14 +26,14 @@
   ],
   "dependencies": {
     "azure-devops-node-api": "^15.1.2",
-    "@uns-kit/core": "3.0.21"
+    "@uns-kit/core": "3.0.23"
   },
   "unsKitPackages": {
-    "@uns-kit/core": "3.0.21",
-    "@uns-kit/api": "3.0.21",
-    "@uns-kit/cron": "3.0.21",
-    "@uns-kit/database": "3.0.21",
-    "@uns-kit/assistant-workflow": "3.0.21"
+    "@uns-kit/core": "3.0.23",
+    "@uns-kit/api": "3.0.23",
+    "@uns-kit/cron": "3.0.23",
+    "@uns-kit/database": "3.0.23",
+    "@uns-kit/assistant-workflow": "3.0.23"
   },
   "scripts": {
     "build": "tsc -p tsconfig.build.json",

package/templates/default/AGENTS.md

@@ -30,6 +30,7 @@ Pointers for AI/code-assist tools when working in this generated project.
 - 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.
 - When crossing `<3.0.7` to `>=3.0.7`, update the application's direct `zod` dependency to Zod 4, migrate Zod-3-only project config extension APIs, and regenerate `config.schema.json` plus `src/config/app-config.ts`.
 - When crossing `<3.0.11` to `>=3.0.11` for an OpenHub 2.x add-on, replace the old `>=7.1 <8` manifest range with `>=2 <3` only after compatibility validation, then use the three credential-free runtime profiles and `ServiceTokenProvider` guidance in `MIGRATIONS.md`.
+- When crossing `<3.0.22` to `>=3.0.22`, API logs use server-generated request IDs rather than URLs or unverified email claims. Reuse `req[Symbol.for("uns.http.request-id")]` in authenticated diagnostics; never restore raw topic/parameter logging or trust caller identity headers.
 - When a project configuration stores database connection values as environment or Infisical references, use `secretValueSchema` for those fields and regenerate `config.schema.json`; retain normal string schemas for non-secret settings.
 
 <!-- uns-kit:migrations:end -->