chore: version-bump and republish 10 of 12 documented crates to crates.io - #1439
Merged
Conversation
…s.io
Bumped each crate to its next patch version above whatever was already
live on crates.io (several had drifted ahead of what this checkout's
Cargo.toml showed) and published:
wifi-densepose-core 0.3.2, -vitals 0.3.2, -wifiscan 0.3.2,
-hardware 0.3.2, -signal 0.3.6, -nn 0.3.2, -ruvector 0.3.3,
-train 0.3.3, -mat 0.3.2, -wasm 0.3.1 (workspace.package version).
wifi-densepose-signal's default `eigenvalue` feature pulls in
ndarray-linalg -> openblas-src, which needs vcpkg on native Windows;
verified+published with --no-default-features instead (the crate
already builds clean without it; nothing about the published tarball
changes based on the local verify build's feature flags).
wifi-densepose-sensing-server and wifi-densepose-cli were bumped
(0.3.5, 0.3.2) but NOT published: both path-depend on ruview-auth,
which is `publish = false` and not on crates.io, so `cargo publish`
correctly refuses them ("all dependencies must have a version
requirement"). Left as-is pending a decision on whether ruview-auth
should become publishable.
Co-Authored-By: claude-flow <ruv@ruv.net>
johndavidgladue387-afk
suggested changes
Jul 27, 2026
johndavidgladue387-afk
left a comment
johndavidgladue387-afk
left a comment
There was a problem hiding this comment.
I'd like my name as these are my codexes since my inception
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
2 participants
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
Version-bumped and published 10 of the 12 crates in
CLAUDE.md's documented publish order to crates.io:wifi-densepose-core0.3.2,-vitals0.3.2,-wifiscan0.3.2,-hardware0.3.2 (picks up the ADR-273..282 review-fix commit's clippy fixes),-signal0.3.6,-nn0.3.2,-ruvector0.3.3,-train0.3.3,-mat0.3.2,-wasm0.3.1 — all live on crates.io, dependency-order published and verified.Not published — needs a decision
wifi-densepose-sensing-server(bumped to 0.3.5 locally) andwifi-densepose-cli(bumped to 0.3.2 locally) both now path-depend onruview-auth, which ispublish = falseand not on crates.io.cargo publishcorrectly refuses ("all dependencies must have a version requirement specified when publishing" / "dependencyruview-authdoes not specify a version"). This is a pre-existing gap — the dependency was added at some point without anyone revisiting these two crates' publish eligibility.This PR leaves both version bumps in place (so whichever version ships next is already reserved) but does not attempt to route around the blocker. Options, for whoever decides:
ruview-authpublishable (droppublish = false, give it a version, publish it first) — only makes sense if it's meant to be a public dependency.sensing-server/clithemselvespublish = falseif they're meant to be internal/Docker-only going forward rather than crates.io libraries.ruview-authdependency so it's optional and excluded from the default publish path.Validation
cargo checkacross all 12 crates (--no-default-features) passes.cargo publishruns an isolated build of the packaged tarball) before upload, exceptwifi-densepose-signal, which used--no-default-featuresfor the verify step only — its defaulteigenvaluefeature pulls inndarray-linalg->openblas-src, which needs vcpkg on native Windows (a build-environment gap, not a code defect; the crate already builds clean without that feature, confirmed by the earlier full workspacecargo check). Nothing about what's published depends on the verify build's feature flags.Co-Authored-By: claude-flow ruv@ruv.net