@duyquangnvx/create-agent-cli 0.19.0 → 0.21.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 +26 -0
- package/dist/bin.js +1037 -983
- package/package.json +2 -2
- package/template/skills/{{binName}}/SKILL.md +5 -13
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,32 @@ What changed in each release of `@duyquangnvx/agent-cli` (the Runtime) and `@duy
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
## v0.21.0 (2026-10-29)
|
|
8
|
+
|
|
9
|
+
### Added
|
|
10
|
+
|
|
11
|
+
- `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.
|
|
12
|
+
|
|
13
|
+
### Changed
|
|
14
|
+
|
|
15
|
+
- **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.
|
|
16
|
+
|
|
17
|
+
### Fixed
|
|
18
|
+
|
|
19
|
+
- 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.
|
|
20
|
+
- 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.
|
|
21
|
+
|
|
22
|
+
## v0.20.0 (2026-10-28)
|
|
23
|
+
|
|
24
|
+
### Changed
|
|
25
|
+
|
|
26
|
+
- **Breaking:** the hints of `OUTPUT_EXISTS` and `ALREADY_EXISTS` read `once the user agrees to replace it, run the Next step` (`them` for several, and `remove` for `skill install` removing an edited file), `NOT_CONFIRMED`'s reads `once the user approves the cost, run the Next step`, and those of `CONFIRMATION_REQUIRED` and `CONFIRMATION_MISMATCH` read `once the user confirms the target, run the Next step`, so an agent asks before adding `--force`, `--yes` or `--confirm` without a skill telling it to. The docs' example `bundle` gives `BUNDLE_EXISTS` the same kind of hint.
|
|
27
|
+
- **Breaking:** the scaffolded skill's Recovering from errors section tells the agent to do what the hint says, and keeps a row only for `LANGUAGE_UNSUPPORTED`, which now asks the user whether an English card will do before running the Next step. The rows for `OUTPUT_EXISTS`, `NOT_CONFIRMED` and every exit code are gone, since the hints and `--help` say the same.
|
|
28
|
+
|
|
29
|
+
### Fixed
|
|
30
|
+
|
|
31
|
+
- `--force` in help reads `replace a file the run writes that already exists; --dry-run lists every file it writes`, since `--dry-run` lists the files a run writes, not which of them exist.
|
|
32
|
+
|
|
7
33
|
## v0.19.0 (2026-10-28)
|
|
8
34
|
|
|
9
35
|
### Added
|