Repository navigation
Fix npm publish treating the tarball path as a GitHub repo - #162
Merged
Merged
Conversation
`npm publish dist/x.tgz` parses `dist/...` as GitHub shorthand and tries to git ls-remote it; use an explicit `./` path. Add the `repository` field that npm provenance / trusted publishing verifies against the source repo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A7iNWzEEZrwfmb3a8J3F7L
rickmark
marked this pull request as ready for review
October 5, 2026 16:21
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.
Summary
The first publish after #161 failed on npm (run). The other three publish workflows succeeded: PyPI, RubyGems and the site.
npm publish dist/<file>.tgzreadsdist/...as GitHubuser/reposhorthand. This PR changes two things:./dist/*.tgzso npm treats the argument as a local tarball.repository(withdirectory: _packages/node) andhomepagetopackage.json. npm provenance and trusted publishing check thatrepository.urlmatches the GitHub repo the workflow runs in.The npm trusted publisher is already configured:
publish-npm.yml, environmentnode-push.Testing
npm publish ./apple-data-*.tgz --dry-runresolves to+ apple-data@1.0.643, the version in the tarball packed from this branch.package.jsoncontains the newrepositoryfield.actionlintpasses.🤖 Generated with Claude Code
https://claude.ai/code/session_01A7iNWzEEZrwfmb3a8J3F7L
Generated by Claude Code