Repository navigation
release(ruv-swarm): npm 2.0.1 to unblock protected-release (WASM receipt digest) - #209
Merged
Merged
Conversation
…ee Rust sources protected-release run 42865774622 published the three 1.0.7 crates. It then failed at its npm step: the ruv-swarm 2.0.0 candidate packs a wasm/build-info.json whose sourceSha256 (refreshed by #205 and #208) differs from the published 2.0.0 tarball. That is the only file that differs in the archive. The npm script refuses an existing version with different bytes, so every release run fails until the version moves. cuda-wasm 2.0.0 is byte-identical to the public archive. - ruv-swarm 2.0.0 -> 2.0.1 in package.json and both lockfiles (the root lockfile's name field is unchanged). - build-info.json sourceSha256 -> a7a4c4c7 (package.json and the lockfiles are digest inputs). The WASM binaries and artifact hashes are unchanged. - The install fixture points at ruv-swarm-2.0.1.tgz, and the smoke test asserts 2.0.1. Its lockfile was regenerated by npm run test:installation (the old one still pinned better-sqlite3 ^11.6.0). - README version line and CHANGELOG entry. No runtime code or dependency change. Checked: verifyWasmBuild OK; npm test (104 + 4 + 8) passes; test:installation (pack, clean install, audit, smoke) passes; npm audit 0 for root, ruv-swarm/npm and the fixture. Co-Authored-By: claude-flow <ruv@ruv.net>
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.
Summary
protected-releaserun 42865774622 publishedruv-swarm-cli,ruv-swarm-mcpandswe-bench-adapter1.0.7 (24 other cratesalready-verified). It then failed at the npm step withPublished npm bytes do not match candidate: ruv-swarm.The only file that differs between main's
ruv-swarmpack and the public 2.0.0 tarball iswasm/build-info.json. ItssourceSha256was refreshed in #205 and #208, after the ruv-swarm Rust crates dropped OpenSSL. The release script refuses an existing version with different bytes, so every release run fails until the version moves.cuda-wasm@2.0.0is byte-identical to its public archive.Changes
ruv-swarm2.0.0 → 2.0.1 inpackage.jsonand both lockfiles.wasm/build-info.jsonsourceSha256→a7a4c4c7…, becausepackage.jsonand the lockfiles are digest inputs. WASM binaries and artifact hashes are unchanged, the same method as fcce144 and fix(ruv-swarm,deps): drop openssl (RUSTSEC-2026-0474/0476/0477); cli/mcp/swe-bench-adapter 1.0.7 #205.ruv-swarm-2.0.1.tgz, and the smoke test asserts 2.0.1. The fixture lockfile was regenerated bynpm run test:installation.No runtime code or dependency changes.
Verification
verifyWasmBuild: OKnpm testinruv-swarm/npm: 104/104, 4/4, 8/8npm run test:installation(real pack → clean install → audit → smoke): passednpm audit: 0 vulnerabilities (root,ruv-swarm/npm, fixture)🤖 Generated with claude-flow