Repository navigation
release: ruv-fann 0.2.3 cascade, rustix 1.1.6, lockfile-aware drift gate (#221) - #223
Merged
Merged
Conversation
The credential-free "Check source binding and all candidate bytes" step now downloads each candidate's version from static.crates.io and fails if it is already public with different bytes, listing every drifted crate. Before, that mismatch was only found inside --publish, after earlier crates in the order had uploaded: run 42957654418 published cuda-rust-wasm 0.2.1 and then stopped at ruv-fann 0.2.2 (#221). Checked: scripts/tests 69/69 (one new preflight case). Co-Authored-By: claude-flow <ruv@ruv.net>
…ip (#221) The published ruv-fann 0.2.2 crate no longer matches the repository: README.md and two docs/assets SVGs changed after it shipped, and the root crate's include list ships them. The protected release's byte gate therefore stopped run 42957654418 at ruv-fann. Root ruv-fann 0.2.2 -> 0.2.3 (no code change). Dependents whose exact version requirement on the root must move (verify-release.py redirect_root) take their next patch version; caret requirements between siblings stay: - ruv-fann-candle 0.1.0 -> 0.1.1 (=0.2.3) - neuro-divergent, -core, -models, -training 0.2.0 -> 0.2.1 - ruv-swarm-ml, ruv-swarm-wasm 1.0.6 -> 1.0.7 - unpublished: bindings/napi, config/rune-probe (=0.2.3), lockfiles The ruv-swarm npm WASM receipt hashes the root and ruv-swarm manifests and locks, so the WASM was rebuilt with the recorded toolchain (rustc 1.88.0, wasm-pack 0.15.1, no RUSTFLAGS); build-info sourceSha256 c39cf477. Release pipeline: - the public Rust consumer pins ruv-fann =0.2.3 and ruv-fann-candle =0.1.1 - publish-candidates.py paces new crate uploads (PUBLISH_SPACING_SECONDS, 420 s in protected-release) for about 10 publishes per hour; publish job timeout 60 -> 150 minutes. Already-public identical versions never wait. Co-Authored-By: claude-flow <ruv@ruv.net>
…uv-fann 0.2.3 and ruv-swarm-wasm 1.0.7) Rebuilt the ruv-swarm WASM receipt for the new manifest (WASM bytes unchanged; sourceSha256 1e9f8667). Co-Authored-By: claude-flow <ruv@ruv.net>
…bout an hour) Co-Authored-By: claude-flow <ruv@ruv.net>
Owner
Author
|
This PR is not merged yet. |
Co-Authored-By: claude-flow <ruv@ruv.net>
… bump binary crates Drift gate (publish-candidates.py, both the credential-free preflight and the publish step): when a published version differs from its candidate only in the embedded Cargo.lock and the package ships no binary (no [[bin]], src/main.rs or src/bin/*.rs, honoring autobins), record "lockfile-only-drift-library" and skip it: no failure, no republish. Cargo never reads a dependency's lockfile, so dependents receive identical source. Packages that ship binaries still fail the gate, because `cargo install --locked` uses that lockfile. The publication receipt carries the public sha256 (plus candidate_sha256), and the public bytes are kept so create-github-release.py attaches exactly what crates.io serves; release notes list such crates. Unreadable published archives remain drift. Four new tests. Locks: rustix 1.0.7 -> 1.1.6 in the root and ruv-swarm lockfiles (RUSTSEC-2026-0486, unsound; cargo-audit 0.22.2 --deny unsound is clean on both). The ruv-swarm resolver also moves bitflags 2.9.1 -> 2.13.2 and linux-raw-sys to 0.12.1. Binary crates whose archives drift: ruv-swarm-cli, ruv-swarm-daa and ruv-swarm-mcp 1.0.7 -> 1.0.8. The eight library crates that drift only in Cargo.lock (claude-parser, agents, benchmarking, core, ml-training, persistence, transport, swe-bench-adapter) are not republished. The ruv-swarm WASM was rebuilt with the recorded toolchain (rustc 1.88.0, wasm-pack 0.15.1, empty RUSTFLAGS); receipt sourceSha256 07d68c45. The WASM bytes change because of the bitflags update. Co-Authored-By: claude-flow <ruv@ruv.net>
…imeout 180 minutes Co-Authored-By: claude-flow <ruv@ruv.net>
ruv-swarm-mcp's test_version_info pins CARGO_PKG_VERSION and failed CI after the 1.0.8 bump. WASM bytes unchanged; receipt sourceSha256 c2b540fe. Co-Authored-By: claude-flow <ruv@ruv.net>
Owner
Author
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
The protected release (run 42957654418) stopped at
ruv-fann: crates.io 0.2.2 holds an older README.md anddocs/assetsSVGs than the repo, and the root crate ships them (#221). Main's lockfiles were also denied by RUSTSEC-2026-0486 (rustix 1.0.7, unsound), so every acceptance run, and therefore every release, failed. The coordinator decided on #221 to keep the no-exceptions audit policy and make the drift gate lockfile-aware.Version map: 12 new crates, no code changes
=0.2.3pinredirect_root)Caret requirements between siblings are unchanged, and no new dependencies are added.
Lockfile-aware drift gate
publish-candidates.pyapplies this rule in both the credential-free preflight and the publish step.Cargo.lock, and the package ships no binary (no[[bin]],src/main.rsorsrc/bin/*.rs, honoringautobins), it is recorded aslockfile-only-drift-library. It does not fail the run and is not republished. Cargo never reads a dependency's lockfile.cargo install --lockeduses the embedded lockfile, so binary crates get no exemption.candidate_sha256), and the GitHub release attaches the public bytes and lists the skipped crates.Four tests cover this.
The eight crates skipped this way: claude-parser 1.0.6, ruv-swarm-agents 1.0.6, ruv-swarm-benchmarking 1.0.6, ruv-swarm-core 1.0.7, ruv-swarm-ml-training 1.0.6, ruv-swarm-persistence 1.0.8, ruv-swarm-transport 1.0.8, swe-bench-adapter 1.0.7.
Also
cargo-audit 0.22.2 --deny unsoundis clean on both.sourceSha256is07d68c45. The WASM bytes change through the bitflags update.ruv-fann =0.2.3andruv-fann-candle =0.1.1.ci.ymlis re-enabled, so this PR runs the full acceptance suite.Checked locally
verify-release.py, run on swarm, forecasting and candle (candle on rustc 1.99.1), with each candidate classified against static.crates.io:The root archive is identical across toolchains. opencv-rust and cuda-wasm are unchanged and were byte-verified in run 42957654418.
scripts/tests: 74/74.🤖 Generated with claude-flow