Repository navigation
fix: verify npm releases using actual dist-tag output - #18
Merged
Merged
Conversation
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 2.8.0 publish succeeded, but the final verification failed because
npm dist-tag ls --jsonstill returnedlatest: 2.8.0as text. Parse the CLI's actual text output and fail if the latest tag is missing, invalid, or does not match the committed version.Add a manual
verify_onlyinput to check a completed release without republishing the immutable npm version. Normal automatic releases continue to run all tests, build and archive checks before publishing.Validation: eight release tests, including the exact observed output and missing/malformed-tag cases; parser exercised against live npm CLI output; actionlint and git diff checks.