Repository navigation
release: prepare npm 2.1.1 and recover verified CI downloads - #743
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.
Deliver the already merged photo-upload path hardening (#740) as npm 2.1.1. Shared, hooks, bridge and setup advance together; daemon and portable fixture versions are mirrored. Root VERSION and all other delivery channels remain unchanged. The owner authorized npm-only publication and resolving the CI outage.
GitHub release download URLs returned persistent HTTP 504, connection timeouts/resets and intermittent API 502. CI now resolves exact official release asset identities and verifies full size and SHA-256 before extraction. Java CodeQL uses the same 2.27.4 bundle; Gradle's version comes from the committed wrapper and retains a checksum. Rust OSV Scanner retains its independent pinned checksum. Only the disposable ESP32 inventory job enables Python transport fallback. API retries are bounded to three attempts and refresh stale redirects. Authentication/TLS failures, unexpected identities, missing unreviewed hashes, corrupt and partial transfers fail closed. Credentials remain confined to non-redirecting API requests; allow-listed GitHub storage receives no credential. Storage 404 responses obtain a fresh link for the same verified asset.
Two pre-digest ROM archives are explicitly pinned by asset ID, size and reviewed SHA-256. The zip's thirteen ELF payloads match the existing installation; its inspected tools.json supplies the upstream tar checksum. These changes neither change npm package bytes nor bypass any scan.
Validation:
After latest required CI passes, merge normally and tag only npm-v2.1.1. Monitor npm Release and read back all four exact versions/latest tags, setup README and GitHub release. Record measured delivery in README, RELEASING and security docs. No tag/upload has been attempted; registry latest remains 2.1.0.