Repository navigation
Point repository metadata at AgenteLabs so npm provenance verifies - #24
Merged
Merged
Conversation
The first @FlashyFinancial publish (0.3.0) was rejected by the registry with E422: the sigstore provenance bundle names the real build source, github.com/AgenteLabs/wdk-staking-kit, and package.json's repository.url still said github.com/FlashyLabs/wdk-staking-kit — the pre-rename org. GitHub redirects the old name; npm's provenance check does not. Updates every self-URL (package.json, README, charter, templates) to the org the repository actually lives in. Sealed records are left as history. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VgrPGGUFKMq9zXBHnfcTgs
The rescope pinned repository/homepage/bugs to the pre-rename org on the reasoning that a scope rename is not a repo move. npm provenance disproved the pin on the first publish: the registry rejects a tarball whose repository.url disagrees with the attested build source. The invariant is the opposite one — these fields follow where the repository actually lives. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VgrPGGUFKMq9zXBHnfcTgs
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.
Summary
Second and last blocker on the first
@flashyfinancial/wdk-staking-kitpublish (run 41018730238):GitHub redirects the pre-rename org name; npm's
--provenancecheck does not — the attested build source must equalrepository.url. Updates every self-URL (package.json, README,flashyos.roles.json, issue-template config, and the two tests that pinned the URL) togithub.com/AgenteLabs/wdk-staking-kit.CHANGELOG.mdand sealed fragments are left as history.Merging touches
package.json, so the publish workflow fires on main and 0.3.0 should land.Test plan
npm ci && npm test— all pass (1 honest skip, unchanged)npm run check— manifest currentnpm view @flashyfinancial/wdk-staking-kit@0.3.0Generated by Claude Code