Repository navigation
Commit 9d76aa1
chore: bump @aictrl/cli to 0.3.5 and @aictrl/util to 1.2.17 (#74)
v0.3.4 release (#71 + #72 fixes) couldn't actually publish @aictrl/cli
because the publish workflow doesn't auto-stamp AICTRL_VERSION into
the main package.json `version` fields — only platform binaries get
the release version. On v0.3.4 the workflow tolerated "already-published"
errors for cli 0.3.3 / util 1.2.16 / sdk 0.1.2 and the smoke test
correctly caught it (ETARGET: No matching version found for
@aictrl/[email protected]).
Bump cli and util so v0.3.5 actually publishes new versions carrying
the resolver + exit-code fixes. Skip sdk: its catalog: deps are only
in devDependencies, ignored by npm consumers, so 0.1.2 is functionally
installable.
Follow-up worth filing: publish.yml should stamp AICTRL_VERSION into
all package manifests, not just platform binaries, so future releases
don't need manual version bumps.
Refs #71 #72
Co-authored-by: Bulat Yapparov <[email protected]>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>1 parent 77d1f7a commit 9d76aa1
2 files changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
0 commit comments