fix(ci): finalize verified published 0.1.2 without republishing - #97
Merged
Conversation
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.
Bounded recovery for the already published 0.1.2 only: protected release environment and existing deploy key; pinned SHA and tarball SHA256; exact registry-byte comparison, official npm signature audit, provenance anchor validation and CLI smoke; create-only atomic v0/v0.1 aliases; publish existing draft. No npm publish or new credentials. Local official audit verifies 21 signatures and 2 attestations; exact package/commit/ref/digest confirmed. Legacy workflow receipt parser remains a separate recorded limitation.