build: add repository metadata required for npm provenance#17
Merged
Conversation
The 2.0.0 publish has failed on every run since #11. The workflow itself was already correct for OIDC trusted publishing (id-token: write, registry-url, no token, pnpm pinned to 10.x). The two missing pieces were external to it: - The Trusted Publisher was never configured on npmjs.com (now done: indexzero/vlurp, release.yml). - package.json had no `repository` field, which npm provenance and the Trusted Publisher matcher both require. Add it (plus bugs/homepage). With both in place, merging to main runs `pnpm changeset publish`, which sees package.json at 2.0.0 (npm latest is 1.2.0) and publishes it with provenance and a v2.0.0 tag. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
indexzero
force-pushed
the
fix/provenance
branch
from
June 30, 2026 19:31
080da49 to
4a4c3d4
Compare
indexzero
changed the title
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.
No
repositoryfield inpackage.json— npm provenance generation and the Trusted Publisher matcher both require it