fix: repository.url for npm provenance validation - #45
Merged
Conversation
Trusted publishing now authenticates (E404 gone) but provenance verification rejects the tarball: package.json carried no repository field, and sigstore validation requires it to match the workflow's repo. Mirrors dspack-gen's shape. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds repository metadata to @aestheticfunction/dspack-emit so npm trusted publishing provenance validation can associate the published artifact with the GitHub repository used by the release workflow.
Changes:
- Add
repository(type + url) topackage.jsonto satisfy npm provenance verification requirements. - Minor formatting/indent normalization on the adjacent
descriptionline.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Trusted publishing auth now works; provenance verification requires
repository.urlmatching the workflow repo, and emit's package.json had none (all prior releases were manual, so it never surfaced). Mirrors dspack-gen. 312/312 green.🤖 Generated with Claude Code