Repository navigation
ci(release): idempotent version-derived GitHub release, 10-min npm visibility wait, ruv.io homepages - #216
Merged
Conversation
… 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>
This was referenced Nov 11, 2026
Merged
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
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)v0.2.2, so every run after the first failed with "Release tag already exists". The tag is now derived from the publishedruv-swarmnpm version:ruv-fann-registry-v<version>..crate/.tgzassets are byte-identical, the step recordsalready-releasedand skips. Receipt JSONs are excluded from the comparison because they embed the source commit.ruv-swarm@2.0.0text.2. npm visibility wait (
scripts/publish-npm-candidates.py)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.publish-candidates.pyhas the same 2-minute loop for crates. It isn't changed here.3.
homepage→ https://ruv.ioruv-swarm,cuda-wasm, and the unpublished@ruv-fann/napiand@ruv-fann/integrations(both previously had no homepage).ruv-swarm2.0.2 andcuda-wasm2.0.1, with CHANGELOG entries marked Unreleased. They ship with the next real release.cuda-wasmversion instead of a hardcoded2.0.0, which would have failed the next run.ruv-swarmpackage.json and lockfiles are WASM receipt inputs, sosourceSha256→5a896c96…. WASM binaries and artifact hashes are unchanged.packages/core,packages/wasmandpackages/wspalready 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 packedruv-swarm-2.0.2.tgzandcuda-wasm-2.0.1.tgz: passed.ruv-swarm/npm:npm test104/104, 4/4, 8/8;npm run test:installationpassed.cuda-wasm:npm test18/18.verifyWasmBuild: OK.npm audit: 0 vulnerabilities (root,ruv-swarm/npm, fixture,cuda-wasm).🤖 Generated with claude-flow