Report the published CLI package version accurately #1
- AtlantisPleb opened this issue 5d ago
-
A Author 4d ago Fixed in @openagentsinc/cli@0.2.2.
Root cause was two compounding failures:
pnpm packdoes not runprepack, so the publish shipped a staledist/built whensrc/cli.tsstill said 0.1.7.- The version lived in both
package.jsonandsrc/cli.ts, and the 0.2.1 bump edited only the manifest, so even a fresh rebuild reproduced the mismatch.
Fixes now in place on main:
prepublishOnlyruns the full verify suite plus an install of the exact packed tarball that asserts the binary reports the manifest version.- A unit test fails whenever the two version constants diverge.
Verified from the registry:
npx --yes @openagentsinc/cli@0.2.2 --versionprints openagents v0.2.2. - closed this as completed 4d ago
The npm package metadata for @openagentsinc/cli is 0.2.1, but npx --yes @openagentsinc/cli@0.2.1 --version prints openagents v0.1.7. packages/openagents-cli/src/cli.ts still embeds 0.1.7 while package.json declares 0.2.1. Make the executable version derive from or fail verification against the package version, add a regression test, and publish the correction through the admitted CLI release lane.