Description
npx tabctl@0.6.0-alpha.9 version reports 0.6.0-alpha.8 instead of 0.6.0-alpha.9.
The GitHub Release binary is correct — mise x github:ekroon/tabctl@v0.6.0-alpha.9 -- tabctl version correctly reports 0.6.0-alpha.9.
Root cause (suspected)
The npm publish step in the release workflow (.github/workflows/release.yml) may have built the binary before the Cargo.toml version was bumped, or cached a stale binary from the previous build.
Steps to reproduce
npx -y tabctl@0.6.0-alpha.9 version
# Expected: 0.6.0-alpha.9
# Actual: 0.6.0-alpha.8
Impact
npm alpha users get a stale binary. Not a functional issue (alpha.8 works) but confusing for version verification.
Description
npx tabctl@0.6.0-alpha.9 versionreports0.6.0-alpha.8instead of0.6.0-alpha.9.The GitHub Release binary is correct —
mise x github:ekroon/tabctl@v0.6.0-alpha.9 -- tabctl versioncorrectly reports0.6.0-alpha.9.Root cause (suspected)
The npm publish step in the release workflow (
.github/workflows/release.yml) may have built the binary before the Cargo.toml version was bumped, or cached a stale binary from the previous build.Steps to reproduce
Impact
npm alpha users get a stale binary. Not a functional issue (alpha.8 works) but confusing for version verification.