Repository navigation
docs: record verified npm 2.1.1 delivery - #744
Merged
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
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.
Record the completed npm 2.1.1 delivery in README, RELEASING and the security runbook. All four exact versions/latest tags and gitHead values match tagged merge b7246c3; npm Release succeeded and the GitHub release is public. The setup README is populated, all four tarballs download and pass registry integrity checks, and the public CLI installation passes native ABI probes with a verified manual Node restart on port 9120.
Preserve the dated November 7 storefront observations for unchanged channels. Record the reviewed manifest/dependency-label differences between the linked local candidate and public archives, alongside the existing full verification receipt and acceptance results.
Validation: pnpm verify:changed passed (documentation links, catalog, preview and Pages parity). This PR changes three Markdown files. The release merge commit's master CI completed successfully, including all eight CodeQL categories, Apple Tests and Pages. Bridge metadata became visible before its tarball stopped returning 404; readback continued until all four actual archives downloaded and passed integrity checks. No tag was replaced or version consumed as a workaround.