Repository navigation
fix(release): recover npm provenance identity without changing frozen v2.1.0 - #60
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Correct the npm Registry E422 source-identity mismatch without changing the signed v2.1.0 tag, manifest, tarballs, or original evidence. Add two successful independent GitHub-hosted rebuilds (run 34754673547), 11 byte-identical frozen artifacts, 22 verified replacement Sigstore bundles, a regression-tested identity validator, and an explicit additive bootstrap recovery path. Local validation: 797 unit tests, lint, typecheck, docs checks, frozen manifest GO, and both historical publication records pass. New-package Registry acceptance remains pending; no full-release success is claimed. Issue #13 remains pending and unchanged.