Skip to content

ci(release): idempotent version-derived GitHub release, 10-min npm visibility wait, ruv.io homepages - #216

Merged
ruvnet merged 1 commit into
mainfrom
ci/release-pipeline-fixes
Nov 10, 2026
Merged

ruvnet merged 1 commit into
mainfrom
ci/release-pipeline-fixes

Conversation

@ruvnet

@ruvnet ruvnet commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

Summary

Three release-pipeline fixes found while shipping ruv-swarm@2.0.1 (#209, run 42879324451). Nothing is published by this PR.

1. GitHub release tag (scripts/create-github-release.py)

  • The tag was hardcoded as v0.2.2, so every run after the first failed with "Release tag already exists". The tag is now derived from the published ruv-swarm npm version: ruv-fann-registry-v<version>.
  • Idempotent: if a published release with that tag exists and its .crate/.tgz assets are byte-identical, the step records already-released and skips. Receipt JSONs are excluded from the comparison because they embed the source commit.
  • Different archives, a draft, or a tag without a release still fail. Tags and releases are never overwritten.
  • Release notes are built from the receipts, replacing the hardcoded PR Add dense autograd with Candle parity, WASM/Node training, and patched native services #202 / ruv-swarm@2.0.0 text.
  • Known edge: a change to crates outside the ruv-swarm WASM digest (neuro-divergent, opencv, cuda-rust-wasm) with no ruv-swarm bump would reuse the same tag with different archives. It fails safely, with a message telling you to bump ruv-swarm.

2. npm visibility wait (scripts/publish-npm-candidates.py)

  • The script waited 24 × 5 s (2 min) after npm publish. In run 42879324451 the tarball stayed 404 longer than that even though the publish was correct.
  • wait_public() now retries 404s for up to 600 s with 5/10/20/30/60 s backoff. Other HTTP errors are raised immediately.
  • A timeout now says "not publicly downloadable" instead of reporting a byte mismatch.
  • publish-candidates.py has the same 2-minute loop for crates. It isn't changed here.

3. homepage → https://ruv.io

  • Set for ruv-swarm, cuda-wasm, and the unpublished @ruv-fann/napi and @ruv-fann/integrations (both previously had no homepage).
  • The release script refuses an existing npm version with different bytes. So that the next run stays clean, the published packages move to unreleased patch versions: ruv-swarm 2.0.2 and cuda-wasm 2.0.1, with CHANGELOG entries marked Unreleased. They ship with the next real release.
  • The public/local consumer check now asserts the candidate's own cuda-wasm version instead of a hardcoded 2.0.0, which would have failed the next run.
  • ruv-swarm package.json and lockfiles are WASM receipt inputs, so sourceSha256 → 5a896c96…. WASM binaries and artifact hashes are unchanged.
  • packages/core, packages/wasm and packages/wsp already have a homepage and belong to the npm/WSP release lanes, so they are unchanged.

Verification

  • python3 -m unittest discover -s scripts/tests: 65 tests OK, including 4 new release cases (identical rerun skips; different archives, draft, or missing version fail) and 3 new visibility cases.
  • consumer() run end to end against locally packed ruv-swarm-2.0.2.tgz and cuda-wasm-2.0.1.tgz: passed.
  • ruv-swarm/npm: npm test 104/104, 4/4, 8/8; npm run test:installation passed.
  • cuda-wasm: npm test 18/18.
  • verifyWasmBuild: OK.
  • npm audit: 0 vulnerabilities (root, ruv-swarm/npm, fixture, cuda-wasm).

🤖 Generated with claude-flow

… visibility wait, ruv.io homepages

Release-pipeline fixes found while shipping ruv-swarm 2.0.1 (#209).

1. GitHub release tag. create-github-release.py hardcoded tag v0.2.2
   and failed on every run after the first. The tag now comes from the
   published ruv-swarm npm version (ruv-fann-registry-v<version>). If a
   published release with that tag already exists and its .crate/.tgz
   assets are byte-identical, the step records "already-released" and
   skips. Receipts are excluded from that comparison because they embed the
   source commit. Different archives, a draft, or a tag without a release
   still fail; tags and releases are never overwritten. Release notes are
   built from the receipts instead of the hardcoded PR #202 text.
2. npm visibility. After npm publish the script waited 24 x 5 s (2 min);
   run 42879324451 published ruv-swarm 2.0.1 correctly but needed longer
   than that. wait_public() now retries 404s for up to 600 s with
   5/10/20/30/60 s backoff, and other HTTP errors are raised immediately.
   A timeout now reports "not publicly downloadable" rather than a byte
   mismatch.
3. homepage https://ruv.io for ruv-swarm, cuda-wasm, @ruv-fann/napi and
   @ruv-fann/integrations (the last two were missing it and are
   unpublished). The release script refuses an existing npm version with
   different bytes, so the published packages move to unreleased patch
   versions: ruv-swarm 2.0.2 and cuda-wasm 2.0.1. Nothing is published
   here; the next real release carries them. The consumer smoke test now
   checks the candidate's cuda-wasm version instead of a hardcoded 2.0.0.
   ruv-swarm package.json and lockfiles are WASM receipt inputs, so
   sourceSha256 moves to 5a896c96. The WASM binaries are unchanged.

packages/core, packages/wasm and packages/wsp already have a homepage and
belong to the npm/WSP lanes; they are left unchanged.

Checked: scripts/tests 72/72 (4 new release cases, 3 new visibility
cases); consumer() run against locally packed ruv-swarm 2.0.2 and
cuda-wasm 2.0.1; ruv-swarm npm test 104+4+8 and test:installation pass;
cuda-wasm npm test 18/18; verifyWasmBuild OK; npm audit 0 (root,
ruv-swarm/npm, fixture, cuda-wasm).

Co-Authored-By: claude-flow <ruv@ruv.net>
@ruvnet
ruvnet merged commit 4ae155a 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