Pack instead of publish for the CI dry-run - #6
Closed
DominicFrei wants to merge 1 commit into
Closed
Conversation
npm publish --dry-run fails on newer npm whenever package.json holds an already released version, which is the normal state of every pull request between releases, so the Node 24 jobs went red on any change once 0.0.2 was published. npm pack --dry-run proves the same packaging and skips only the registry version check, which the real publish in the release workflow still enforces.
Contributor
Author
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
2 participants
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.
Refs GAF-668
The Node 24 CI jobs fail on every pull request since 0.0.2 went to npm: newer npm rejects
npm publish --dry-runwhen package.json holds an already released version, and between releases that is always the case.npm pack --dry-run, which proves the same packaging (same pack machinery, same file list) without the registry version check.npm publish, so release-time validation is unchanged.