@deepdockai/cli 1.0.22 → 1.0.23

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 1.0.23
+
+- An incident's program version is named `programVersion` instead of `version`, in `GET /v1/incidents`, in `incidents list --json` and in the skill's concepts. Read the new name where you read the old one; the value is unchanged.
+
 ## 1.0.22
 
 - `keys create --write-env` writes `DEEPDOCK_BASE_URL=<url>` beside the key when `DEEPDOCK_BASE_URL` points the CLI at another API than production, since a key works only on the API it was created on and the bundled clients default to production. A production key points such a line, left by an earlier key, at production. `meta.written.baseUrl` names the URL when the line was written. Revoking a key removes only the key line.

package/dist/deepdock.js

@@ -11429,7 +11429,7 @@ import { spawn } from "node:child_process";
 import { homedir, hostname } from "node:os";
 
 // src/version.ts
-var VERSION = "1.0.22";
+var VERSION = "1.0.23";
 
 // src/runtime.ts
 var DEFAULT_BASE_URL = "https://api.deepdock.ai";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepdockai/cli",
-  "version": "1.0.22",
+  "version": "1.0.23",
   "description": "Deepdock partner CLI: pair devices, see systems and actions, create the API key your code runs them with.",
   "type": "module",
   "license": "MIT",

package/skill/references/concepts.md

@@ -95,7 +95,8 @@ Each pause opens an **incident** (`GET /v1/incidents`). Only Deepdock lifts a pa
 customer's site see that an action is paused but cannot resume it; there is no partner call to
 resume. A stopped or missing system needs no resume: its incident closes once the system is back.
 
-An incident has `id`, `system`, `version`, `action` (`null` for a system-level incident), `reason`,
+An incident has `id`, `system`, `programVersion` (the version of the vendor's program its devices
+run, `null` when they reported none), `action` (`null` for a system-level incident), `reason`,
 `openedAt`, `closedAt`, and `devices` with `deviceId`, `pausedAt`, `resumedAt` and `inactiveAt`. It
 closes once none of its devices is still paused. `GET /v1/incidents` lists incidents that are open
 or closed within the last 30 days, newest first, at most 100.