Skip to content

Fix installed-package smoke tarball discovery - #1

Merged
firegrass merged 1 commit into
mainfrom
agent/BKLG-20261019-y295-proof-cli-s-installed-package-smoke
Oct 19, 2026
Merged

firegrass merged 1 commit into
mainfrom
agent/BKLG-20261019-y295-proof-cli-s-installed-package-smoke

Conversation

@firegrass

Copy link
Copy Markdown
Contributor

npm pack can write lifecycle output before its JSON, causing the installed-package smoke to fail while parsing the tarball filename. Pack into a dedicated temporary directory and require exactly one .tgz file, so package discovery is independent of npm output. The existing installed CLI assertions remain in place, and the entire temporary prefix is removed on success or failure.

Packet: BKLG-20261019-y295

Validation: the workflow recorded its local gate as passed for commit 030dfda8d1b13294c6bbf822c21eb25e5c1dbe2c (tree 5d898f3b9e061e36d6f0b995ef18e485a2368b23): frozen-lockfile install, pnpm typecheck, pnpm test, pnpm build, node scripts/verify-package.mjs, pnpm pack:dry-run, and pnpm smoke:pack.

Packet: BKLG-20261019-y295

Pack into a temporary directory and require a single .tgz so npm 10 prepare output cannot corrupt tarball discovery. Keep the installed CLI assertions and remove the entire prefix on success or failure.
@firegrass
firegrass merged commit 790e314 into main Oct 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant