@dvmkit/dvmctl 0.3.2-rc.1 → 0.3.4-rc.1

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/README.md CHANGED
@@ -6,7 +6,7 @@ Install this exact release:
6
6
 
7
7
  <!-- x-release-please-start-version -->
8
8
  ```bash
9
- npm install -g @dvmkit/dvmctl@0.3.2-rc.1
9
+ npm install -g @dvmkit/dvmctl@0.3.4-rc.1
10
10
  ```
11
11
  <!-- x-release-please-end -->
12
12
 
@@ -14,7 +14,7 @@ Install the complete bundled skill directory so its references remain available:
14
14
 
15
15
  <!-- x-release-please-start-version -->
16
16
  ```bash
17
- npm install --ignore-scripts --prefix "$HOME/.dvmkit" @dvmkit/dvmctl@0.3.2-rc.1
17
+ npm install --ignore-scripts --prefix "$HOME/.dvmkit" @dvmkit/dvmctl@0.3.4-rc.1
18
18
  skill_dir="$(dirname "$(NODE_PATH="$HOME/.dvmkit/node_modules" node -p "require.resolve('@dvmkit/dvmctl/skill')")")"
19
19
  ```
20
20
  <!-- x-release-please-end -->
@@ -37,6 +37,8 @@ For another agent harness, copy the complete directory to its project-skill loca
37
37
 
38
38
  Create a project with `dvmctl create my-dvm`, then run `cd my-dvm && npm install`. Use `dvmctl validate` before deployment. Run `dvmctl dev handler.ts` for local development or `dvmctl serve handler.ts` for the production server. Serving requires a configured handler and any database or payment environment variables that handler uses.
39
39
 
40
+ For automation that supplies deployment secrets, use `dvmctl deploy --target cloud --env-stdin`. Pipe a JSON object whose values are strings into stdin; these values override the project's `.env` for that deployment without changing the file. Input is limited to 64 KiB and must finish within 5 seconds. A terminal, empty input, malformed JSON, and non-string values fail before any deployment work. Local, self-host, connect-tier, and dry-run deployments reject this flag before reading input. Send secrets through the pipe rather than command arguments. Without this flag, deployment keeps its existing `.env` behavior.
41
+
40
42
  The repository field exists only for npm trusted-publishing identity. The source repository is private and currently unavailable to package users; it is not a public source-provenance link.
41
43
 
42
44
  For private-beta security reports while the source is private, email [security@dvmkit.com](mailto:security@dvmkit.com).