Repository navigation
fix: read npm 12 pack output in the tarball check (0.4.1) - #4
Merged
Merged
Conversation
npm 12 prints `npm pack --json` as an object keyed by package name, not an array. The v0.4.0 release failed on this, so nothing was published for it. 0.4.1 carries the same changes.
|
Apercu Cloudflare Pages : https://pr-4.bloub-app.pages.dev |
This branch was successfully deployed
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
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.
The
v0.4.0publish run failed intest:tarball: npm 12 (npm@latestinpublication.yml) printsnpm pack --jsonas an object keyed by package name, not an array. Nothing was published for 0.4.0.tools/test-package-tarball.mjsreads both shapes and fails with the output when neither matches.Checks:
bun run test:tarballpasses with npm 11.6.1 and npm 12.1.0.After merge: tag
v0.4.1.