Fix npm release provenance - #37
Merged
Merged
Conversation
ejsmith
marked this pull request as ready for review
July 29, 2026 00:47
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.
Summary
deno packRoot cause
The v1.3.4 release workflow built, tested, and published to JSR successfully. npm rejected the generated tarball with
E422becausepackage.json.repository.urlwas missing and therefore did not match the GitHub repository in the signed provenance bundle.Recovery
After this merges, dispatching CI with
release_version=1.3.4will publish the corrected tarball to npm and GitHub Packages while skipping JSR.Validation
deno task format-checkdeno task lintdeno task checkdeno task test(200 tests)repository.url = https://github.com/FoundatioFx/FetchClientnpm publish fetchclient.tgz --dry-run --provenance --access public