Accept npm first-version latest tag - #10
Merged
Merged
Conversation
npm assigns latest to a package's sole first version and rejects authenticated removal. Accept that tag only when it points to the sole reviewed version, record it in verification evidence, and retain rejection of any different target.
Correct stale pre-publication README text, document the npm install path, and explicitly preserve the verifier's accepted no-latest state.
Owner
Author
|
Independent AI review of exact head 8c84754: PASS. Initial review found stale public release-status text (P2) and a missing explicit no-latest regression (P3); both were corrected. Re-review found no P0, P1, P2, or new findings and approved this exact head. This records AI review, not human approval. |
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.
Incident
Bootstrap run 30652935848 published all four exact packages, revoked the token, then failed because npm assigned latest to each sole first version. Authenticated removal returned HTTP 400 with both npm 10.9.8 and 11.16.0.
Fix
Verification
No package was republished and the bootstrap workflow was not rerun.