@dashai/cli 0.22.0 → 0.23.0

package/README.md

@@ -807,3 +807,38 @@ The CLI persists state at `$XDG_CONFIG_HOME/dashwise/auth.json` (typically `~/.c
 ## License
 
 MIT
+
+### `dashwise module release [slug]`
+
+Release code already pushed to the module's linked GitHub repository. This uses
+saved `dashwise login` authentication and the same release admission as the
+Builder and MCP. It does not upload local files. The backend must include the
+repository release contract from `Intuize/dashwise-backend#985`.
+
+```bash
+dashwise module release my-module --commit-sha <full-40-character-sha> --yes
+dashwise module release my-module --build 51
+```
+
+The positional slug wins over `module.json` in `--dir` (default current directory).
+For a new release, `--commit-sha` is required and must already exist in the linked
+repository. Branch names, abbreviated SHAs and an inferred latest push are not
+accepted. `--bump patch|minor|major` defaults to `minor`, matching the repository
+API. Release asks for confirmation only when both stdin and stdout are interactive
+and JSON mode is off. Redirected streams and `--json` require explicit `--yes`.
+
+The command waits for the build and prints the build ID, immutable revision and
+released version. `--no-wait` returns once accepted: exit 0 then means queued,
+not released. `--timeout <seconds>` defaults to 360; exit 4 means the wait expired.
+Resume checking with `--build <id>`; this performs only reads and cannot enqueue
+another version. Do not combine it with `--commit-sha`, `--bump` or `--no-wait`.
+An ambiguous enqueue/network failure is not retried automatically; check the
+module's build history in Dashwise before requesting another release.
+
+`--json` emits one result or error on stdout. Success includes `id`, `commit_sha`,
+`version` and `module_version_id`; timeout includes `build_id`, `timed_out` and
+`resume_command`. Refusals and failed builds return nonzero (exit 3 for known
+missing-grant refusals, otherwise 1). Access revoked while waiting stops polling.
+Release creates a version; installing or updating it in Live remains a human
+action. For a module without a linked repository, use the local
+`dashwise module publish` flow instead.