Uh oh!
There was an error while loading. Please reload this page.
fix: add repository metadata so npm provenance validation passes - #30
Merged
Conversation
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Uh oh!
There was an error while loading. Please reload this page.
5 tasks
nicosampler added a commit
that referenced
this pull request
Aug 3, 2026
… 0.2.2 (#31) ## Summary No related issue. The empty changeset added in #30 was meant to satisfy the changeset check without bumping the version, but changesets/action treats "only empty changesets" as pending work: it neither opens a Version PR nor publishes. Removing it unblocks the publish of the already-versioned 0.2.2. ## Changes - Delete `.changeset/puny-knives-roll.md` (empty changeset) ## Acceptance criteria - [ ] On merge, the Release workflow publishes `@bootnodedev/canton-barebones@0.2.2` with provenance ## Test plan ### Automated tests No automated tests added — no package code changes. ### Manual verification `npx changeset status --since=origin/main` passes (no package changes require a changeset). After merge, watch the Release run publish 0.2.2. ## Breaking changes None. ## Checklist - [x] Self-reviewed my own diff - [ ] Tests added or updated - [ ] Docs updated (if applicable) - [x] No unrelated changes bundled in ## Screenshots None.
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 freeto 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
No related issue. Publishing 0.2.2 from CI failed with E422: npm's sigstore
provenance check requires
repository.urlinpackage.jsonto match theGitHub repository the workflow runs from, and the field was missing.
Changes
repositoryfield (git+https://github.com/BootNodeDev/canton-barebones.git) topackage.jsonpackage-lock.jsonAcceptance criteria
mainpublishes@bootnodedev/canton-barebones@0.2.2with provenanceTest plan
Automated tests
npm test— 30/30 pass. No new tests; metadata-only change.Manual verification
Merge and watch the Release workflow publish 0.2.2 to npm.
Breaking changes
None.
Checklist
Screenshots
None.