@deepdockai/cli 1.0.8 → 1.0.10
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
CHANGED
|
@@ -1,5 +1,14 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.10
|
|
4
|
+
|
|
5
|
+
- `GET /v1/devices` and `GET /v1/incidents` page with a cursor: the answer is `{ items, nextCursor }`, with `limit` (1 to 500, default 100) and `cursor` query parameters. The agent skill's key and pairing reference says how to loop over the pages, and the pinned device API carries the new shape. The CLI lists devices through `/partner`, which is unchanged.
|
|
6
|
+
- The pinned device API documents the per-key `429 rate_limited` (600 calls and 120 writes per minute per API key, `Retry-After`).
|
|
7
|
+
|
|
8
|
+
## 1.0.9
|
|
9
|
+
|
|
10
|
+
- The CLI knows `device_learning_only` (exit code 2, refused): the PC runs the Deepdock client for learning only, which runs no actions, so action calls and the systems list on it are refused before anything is sent. It changes only when the Deepdock service is installed on that PC; retrying does not help. The skill's error reference lists it.
|
|
11
|
+
|
|
3
12
|
## 1.0.8
|
|
4
13
|
|
|
5
14
|
- The CLI knows `system_version_unverified` (exit code 3, retry later): a write on a customer system whose vendor version Deepdock has not verified yet is refused before anything is sent, and works once Deepdock has verified that version (`reason: unverified_version`). A version the API cannot parse (`reason: unparseable`) does not clear by waiting: contact Deepdock. Reads are unaffected.
|
package/dist/deepdock.js
CHANGED
|
@@ -10859,6 +10859,7 @@ var EXIT_CODES = {
|
|
|
10859
10859
|
invalid_input: 2,
|
|
10860
10860
|
pairing_code_invalid: 2,
|
|
10861
10861
|
other_partner_build: 2,
|
|
10862
|
+
device_learning_only: 2,
|
|
10862
10863
|
rate_limited: 2,
|
|
10863
10864
|
target_rejected: 2,
|
|
10864
10865
|
check_failed: 2,
|
|
@@ -11427,7 +11428,7 @@ import { spawn } from "node:child_process";
|
|
|
11427
11428
|
import { homedir, hostname } from "node:os";
|
|
11428
11429
|
|
|
11429
11430
|
// src/version.ts
|
|
11430
|
-
var VERSION = "1.0.
|
|
11431
|
+
var VERSION = "1.0.10";
|
|
11431
11432
|
|
|
11432
11433
|
// src/runtime.ts
|
|
11433
11434
|
var DEFAULT_BASE_URL = "https://api.deepdock.ai";
|
package/package.json
CHANGED
|
@@ -87,7 +87,7 @@ curl -X POST "$BASE/v1/devices" \
|
|
|
87
87
|
(`id`, `label`, `hostname`, `os`, `clientVersion`, `status`, `lastSeenAt`, `claimedAt`, `outdated`, `systems`,
|
|
88
88
|
and `updateAvailable` when it runs an older build); `hostname`, `os` and `clientVersion` are `null`
|
|
89
89
|
until the device has reported them. Keep `id`: it is the `deviceId` of every later call.
|
|
90
|
-
`GET /v1/devices` lists your devices and `GET /v1/devices/{deviceId}` reads one
|
|
90
|
+
`GET /v1/devices` lists your devices a page at a time (`{ items, nextCursor }`; pass `nextCursor` back as `cursor` until it is `null`, `limit` 1 to 500, default 100), and `GET /v1/devices/{deviceId}` reads one; each device has the same shape. `GET /v1/incidents` pages the same way.
|
|
91
91
|
|
|
92
92
|
4. Release with `DELETE /v1/devices/{deviceId}`; the device then shows a new code.
|
|
93
93
|
|
|
@@ -35,6 +35,7 @@ dashboard-only.
|
|
|
35
35
|
| `access_missing` | 409 | the device's database access is gone (a removed database account or a lost secret on the PC); every action of that system is refused. Nothing was run. **No `Retry-After`** | as `access_outdated` | as `access_outdated` |
|
|
36
36
|
| `pairing_code_invalid` | 404 | pairing: the code is unknown, expired, replaced, used, or its device is offline | with a fresh code | "read the code off the device screen again" |
|
|
37
37
|
| `other_partner_build` | 409 | pairing: the device runs another partner's client build | no | "this device is set up for another provider" |
|
|
38
|
+
| `device_learning_only` | 409 | the PC runs the Deepdock client for learning only, which runs no actions; nothing was sent to it. Reads, writes and the systems list on it all answer this | no; it changes only when the Deepdock service is installed on that PC | "this PC needs the Deepdock service to run actions" |
|
|
38
39
|
|
|
39
40
|
## Input
|
|
40
41
|
|
|
@@ -87,6 +88,7 @@ const REACTION: Record<string, Reaction> = {
|
|
|
87
88
|
action_not_configured: 'stop',
|
|
88
89
|
pairing_code_invalid: 'fix-input',
|
|
89
90
|
other_partner_build: 'stop',
|
|
91
|
+
device_learning_only: 'stop',
|
|
90
92
|
invalid_input: 'fix-input',
|
|
91
93
|
target_rejected: 'fix-input',
|
|
92
94
|
unknown_author: 'fix-input',
|