Skip to content

release(ruv-swarm): npm 2.0.1 to unblock protected-release (WASM receipt digest) - #209

Merged
ruvnet merged 1 commit into
mainfrom
release/ruv-swarm-npm-2.0.1
Nov 10, 2026
Merged

ruvnet merged 1 commit into
mainfrom
release/ruv-swarm-npm-2.0.1

Conversation

@ruvnet

@ruvnet ruvnet commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Summary

protected-release run 42865774622 published ruv-swarm-cli, ruv-swarm-mcp and swe-bench-adapter 1.0.7 (24 other crates already-verified). It then failed at the npm step with Published npm bytes do not match candidate: ruv-swarm.

The only file that differs between main's ruv-swarm pack and the public 2.0.0 tarball is wasm/build-info.json. Its sourceSha256 was 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.0 is byte-identical to its public archive.

Changes

No runtime code or dependency changes.

Verification

  • verifyWasmBuild: OK
  • npm test in ruv-swarm/npm: 104/104, 4/4, 8/8
  • npm run test:installation (real pack → clean install → audit → smoke): passed
  • npm audit: 0 vulnerabilities (root, ruv-swarm/npm, fixture)

🤖 Generated with claude-flow

…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>
@ruvnet
ruvnet merged commit 48d9374 into main Nov 10, 2026
64 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant