camstack 1.2.213 → 1.2.215
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 +13 -0
- package/README.md +6 -0
- package/dist/chunk-37A556YF.js +822 -0
- package/dist/chunk-BYNP7S4W.js +56 -0
- package/dist/chunk-JPGJK5DC.js +75 -0
- package/dist/{chunk-MJJWVAEM.js → chunk-WGHOCSCW.js} +67526 -67068
- package/dist/cli.js +127 -70
- package/dist/doctor-command-S7Q2U6HO.js +227 -0
- package/dist/{launcher-6TBFW332.js → launcher-RUHSCWRY.js} +332159 -330087
- package/dist/{server-EFXGQ7FD.js → server-7C635XXX.js} +241 -1016
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [1.2.215] - 2026-10-31
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
|
|
14
|
+
- The automation interview accepts a domain target for a step and writes the target shape
|
|
15
|
+
|
|
16
|
+
## [1.2.214] - 2026-10-31
|
|
17
|
+
|
|
18
|
+
### Changed
|
|
19
|
+
|
|
20
|
+
- Every failing MCP tool now reports isError, and hub calls trust only the CA pinned for that hub instead of skipping TLS verification
|
|
21
|
+
- New `camstack mcp doctor` checks Node, hub, pinned CA, session, token scope and CLI version; `camstack login --token-file` logs in without a TTY from a 0600 file
|
|
22
|
+
|
|
10
23
|
## [1.2.213] - 2026-10-30
|
|
11
24
|
|
|
12
25
|
### Changed
|
package/README.md
CHANGED
|
@@ -13,3 +13,9 @@ Package `camstack` on npm.
|
|
|
13
13
|
See [CHANGELOG.md](./CHANGELOG.md) for what changed in each version.
|
|
14
14
|
|
|
15
15
|
<!-- readme:generated:end -->
|
|
16
|
+
|
|
17
|
+
## MCP: doctor, token files, restarts
|
|
18
|
+
|
|
19
|
+
- `camstack mcp doctor` is a read-only check of Node (>= 24), the hub, its pinned CA, the session or token file, the token scope (admin or not) and the CLI version against npm. Each line is ok / fail / unknown with a fix hint, and no token is ever printed.
|
|
20
|
+
- `camstack login <host> --token-file <path>` logs in without a TTY: the token comes from a file only you can read (`chmod 600`; a looser file is refused), is checked against the hub and cached like the interactive login. A token is never accepted through argv or the environment.
|
|
21
|
+
- MCP clients such as OpenCode keep running the old `camstack mcp` process: restart them after the CLI updates.
|