Repository navigation
fix(release): cuda-rust-wasm 0.2.1 so ruv-swarm 2.0.2 can release; 10-minute crates.io wait - #219
Merged
Merged
Conversation
…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>
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.
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-wasmcrate is built fromcuda-wasm/, so its archive includes that directory'spackage.json,README.mdandCHANGELOG.md. #216 changed all three and kept the crate at 0.2.0, which is already on crates.io.publish-candidates.pywould then fail withPublished version exists with different bytes: cuda-rust-wasm.I checked this by packaging locally and diffing against
static.crates.io.package.jsonandCHANGELOG.mddiffer 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-wasm0.2.0 → 0.2.1 inCargo.tomlandCargo.lock. No Rust code changes.cuda-rust-wasm0.2.1cuda2rust,code-generationandnodejs, taking the count from 6 to 9 (ADR-356 asks for 8–20).publish-npm-candidates.py: the public consumer now installs thecuda2rustthis 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/68cargo build --lockedincuda-wasm:cuda2rust 0.2.1npm test --prefix cuda-wasm: 18/18tests/cli-integration.cjspasses against the built binaryAfter merge, the protected release goes out from the merge commit and publishes:
ruv-fann-registry-v2.0.2🤖 Generated with claude-flow