Skip to content

fix(release): cuda-rust-wasm 0.2.1 so ruv-swarm 2.0.2 can release; 10-minute crates.io wait - #219

Merged
ruvnet merged 1 commit into
mainfrom
release/cuda-rust-wasm-0.2.1
Nov 11, 2026
Merged

ruvnet merged 1 commit into
mainfrom
release/cuda-rust-wasm-0.2.1

Conversation

@ruvnet

@ruvnet ruvnet commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Why

PR #216 left ruv-swarm 2.0.2 and cuda-wasm 2.0.1 ready to release, but the protected release would stop before npm. The cuda-rust-wasm crate is built from cuda-wasm/, so its archive includes that directory's package.json, README.md and CHANGELOG.md. #216 changed all three and kept the crate at 0.2.0, which is already on crates.io. publish-candidates.py would then fail with Published version exists with different bytes: cuda-rust-wasm.

I checked this by packaging locally and diffing against static.crates.io. package.json and CHANGELOG.md differ for cuda-rust-wasm 0.2.0. ruv-swarm-cli, ruv-swarm-mcp and swe-bench-adapter 1.0.7 match, apart from .cargo_vcs_info.json.

Changes

  • cuda-rust-wasm 0.2.0 → 0.2.1 in Cargo.toml and Cargo.lock. No Rust code changes.
  • cuda-wasm README:
    • removes the stale "staged / publication is a separate step" wording
    • installs cuda-rust-wasm 0.2.1
  • cuda-wasm keywords: adds cuda2rust, code-generation and nodejs, taking the count from 6 to 9 (ADR-356 asks for 8–20).
  • publish-npm-candidates.py: the public consumer now installs the cuda2rust this release publishes (=0.2.1).
  • publish-candidates.py: the crates.io visibility wait now matches the npm path, 600 s with 5/10/20/30/60 s backoff (it was 24 × 5 s). A timeout reports "not publicly downloadable". Three new tests.

Checked

  • python3 -m unittest discover -s scripts/tests: 68/68
  • cargo build --locked in cuda-wasm: cuda2rust 0.2.1
  • npm test --prefix cuda-wasm: 18/18
  • tests/cli-integration.cjs passes against the built binary

After merge, the protected release goes out from the merge commit and publishes:

  • ruv-swarm 2.0.2
  • cuda-wasm 2.0.1
  • cuda-rust-wasm 0.2.1
  • GitHub release ruv-fann-registry-v2.0.2

🤖 Generated with claude-flow

…ass its byte gate; 10-minute crates.io wait

PR #216 bumped cuda-wasm (npm) to 2.0.1 but left the cuda-rust-wasm crate at
0.2.0, which is already on crates.io. The crate archive packs the same
directory, including package.json, README.md and CHANGELOG.md, so the new
candidate no longer matches the published 0.2.0 bytes and
publish-candidates.py would stop the protected release with "Published
version exists with different bytes: cuda-rust-wasm". Verified by packaging
locally and diffing against static.crates.io: package.json and CHANGELOG.md
differ; the three ruv-swarm crates match.

- cuda-rust-wasm 0.2.0 -> 0.2.1 (Cargo.toml, Cargo.lock). No Rust code change.
- cuda-wasm README: drop the "staged / publication is a separate step"
  wording (0.2.0 is already published) and install 0.2.1.
- cuda-wasm keywords: add cuda2rust, code-generation, nodejs (6 -> 9).
- publish-npm-candidates.py: the public consumer installs the cuda2rust
  that this release publishes (=0.2.1) instead of =0.2.0.
- publish-candidates.py: replace the 24 x 5 s crates.io visibility loop with
  the same 600 s, 5/10/20/30/60 s backoff the npm path uses; a timeout reports
  "not publicly downloadable" instead of failing silently. Three new tests.

Checked: scripts/tests 68/68; cargo build --locked (cuda2rust 0.2.1);
cuda-wasm npm test 18/18; cli-integration against the built binary.

Co-Authored-By: claude-flow <ruv@ruv.net>
@ruvnet
ruvnet merged commit 5ed9ab2 into main Nov 11, 2026
5 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