@duyquangnvx/create-agent-cli 0.20.0 → 0.22.0
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
|
@@ -4,6 +4,33 @@ What changed in each release of `@duyquangnvx/agent-cli` (the Runtime) and `@duy
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
## v0.22.0 (2026-11-02)
|
|
8
|
+
|
|
9
|
+
### Added
|
|
10
|
+
|
|
11
|
+
- The hint of `UNKNOWN_OPTION`, `UNKNOWN_COMMAND` and `INVALID_INPUT` names each Skill copy whose `metadata.version` differs from the build's, for a Skill Hub or a Packaged skill, and says to run `doctor` to update it. A CLI's skill can drop its line on a flag or Command it names that the CLI does not know.
|
|
12
|
+
- The scaffolded setup reference of a Global install says what to do when the user installed the CLI but the shell finds none, under nvm. A CLI's skill can drop its own `command not found` row.
|
|
13
|
+
|
|
14
|
+
### Changed
|
|
15
|
+
|
|
16
|
+
- `REGISTRY_AUTH` from npm's `E403` under a Coding agent hints that the agent's sandbox may refuse the registry: the user types `!` and runs it again, or allows the registry in the sandbox's network list, and logs in only if it fails outside the sandbox too. `update`, the install and `doctor`'s `registry` row all give it. A CLI's skill can drop its row saying that `REGISTRY_AUTH` is no refused login, and its `INTERNAL` row too: that hint already names `<NAME>_DEBUG=1`.
|
|
17
|
+
- The scaffolded skill drops what the agent sees anyway: `SKILL.md` loses its When to use section, which belongs in the description, its paragraph on `--json`, `--dry-run` and `--confirm`, and its description of the error format; the setup reference's Check no longer describes `doctor`'s rows. The shipping guide says a skill line earns its place only when no `--help`, output, hint or `doctor` row says it.
|
|
18
|
+
|
|
19
|
+
## v0.21.0 (2026-10-29)
|
|
20
|
+
|
|
21
|
+
### Added
|
|
22
|
+
|
|
23
|
+
- `install: { mode: "global", registry }` declares a Global install's Install registry, from which `update` and `doctor` install and check the CLI, for users who install from a mirror of the registry releases publish to. It needs no `publishConfig.registry`, which `install: "global"` still reads.
|
|
24
|
+
|
|
25
|
+
### Changed
|
|
26
|
+
|
|
27
|
+
- **Breaking:** a `doctor` problem without a fix gives `doctor` as typed as its Next step, under the hint `fix what the row says, then run the Next step`, in place of no Next step under `the row says what is wrong`. An advisory problem without a fix ends `next` with that line.
|
|
28
|
+
|
|
29
|
+
### Fixed
|
|
30
|
+
|
|
31
|
+
- A `doctor` row that throws a `CliError` with Next steps gives the first one other than `ctx.rerun()` as its `fix`, instead of a hint promising a Next step the row lacked.
|
|
32
|
+
- A `doctor` row whose `ctx.spawn` finds a tool the CLI declares in `tools` missing from `PATH` is `skipped`, saying that tool's row says why, instead of a second problem whose hint promised a Next step it lacked.
|
|
33
|
+
|
|
7
34
|
## v0.20.0 (2026-10-28)
|
|
8
35
|
|
|
9
36
|
### Changed
|