fix(release): add repository field to package.json for provenance - #47
Merged
Conversation
…ification The publish step now reaches npm with a signed OIDC provenance attestation, but npm rejects the publish with: E422 422 Unprocessable Entity Error verifying sigstore provenance bundle: Failed to validate repository information: package.json: "repository.url" is "", expected to match "https://github.com/deessejs/errors" from provenance Adds the missing repository field to packages/errors/package.json so the value matches the URL in the provenance attestation. This was the only remaining blocker for the first trusted-publishing release. Adds a changeset to pass the new ci.yml lint.
5 tasks
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 trusted publishing flow now reaches npm with a signed provenance attestation, but npm rejects with E422:
The fix is one missing field:
packages/errors/package.jsonhad norepositoryblock. npm uses it to verify the package is genuinely from the same repo the OIDC token was minted for.Change
Add
"repository": { "type": "git", "url": "https://github.com/deessejs/errors.git" }topackages/errors/package.json.Effect
Next merge of this branch (or any other PR adding a changeset) triggers the release workflow. With the repository field set, the provenance check passes, and the publish goes through.
🤖 Generated with Claude Code