Fix npm publish resolving release tarball as a GitHub spec - #10135
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request fixes the publish-npm workflow step so npm publish treats the generated release tarballs as local files rather than interpreting tarballs/<name>.tgz as GitHub owner/repo shorthand.
Changes:
- Prefix tarball paths with
./when invokingnpm publishto force local-file resolution.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This was referenced Aug 9, 2026
Merged
Open
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.
Summary
publish-npmpassed each tarball tonpm publishas a baretarballs/<name>.tgzpath. npm reads a slashed argument without a leading./as the GitHubowner/reposhorthand, so it rangit ls-remote ssh://git@github.com/tarballs/<name>.tgzand failed withPermission denied (publickey)instead of publishing the local tarball. This broke the16.6.0-p.1release after the NuGet packages and Nitro operations had already published../so npm resolves it as a local file.Test plan
yamlparse of the workflow and a structural check of the publish phase (gating, ordering, idempotency) pass.16.*release tag (side-effecting) and was not run.