Repository navigation
Fix local archive path in npm release job - #2
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
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.
The release job passed a relative tarball path without
./, which npm interpreted as a GitHub repository shorthand and tried to fetch over SSH. Use an explicit local path and fail early if the downloaded archive is missing.Validation: npm publish with the corrected path passes in dry-run mode, and actionlint passes. Version 0.9.5 remains unpublished, so merging this fix retries it through the normal release workflow.
Note
Add archive existence check before
npm publishin CI release jobAdds a file-existence guard in the release publish workflow step so the job fails early when the expected release archive is missing, rather than proceeding to
npm publish.Macroscope summarized fe09e0b.