ci: verify npm package contents#5
Merged
Merged
Conversation
leblancfg
force-pushed
the
vi/check-package-tarball
branch
from
June 26, 2026 00:09
ffa8ce7 to
9add283
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
CI builds and smoke-tests the dist output, but it does not verify the npm package that would be published. A change can pass tests while accidentally omitting files from the tarball because of the
filesallowlist, build output drift, or package metadata changes.For a pi extension, that is a sharp failure mode: install-time packaging problems show up only after release.
Change
npm pack --dry-runin CI afterpnpm run smoke:dist.Verification
npm pack --dry-rungit diff --check