Repository navigation
v0.3.0
cargo-tops v0.3.0 (protocol 1.1.0)
Package plane only. Protocol stays 1.1.0.
Changes since v0.2.0 (e0fa684, 2026-10-21).
crates.io
cargo-tops 0.3.0 is not on crates.io. cargo publish failed package verification on this tag: crates/cargo-tops/src/profile_data.rs embeds the repo-root class profiles with include_str!("../../../profiles/..."). Those files live outside the crate, and the package include list does not ship them, so the crates.io tarball cannot build. Workspace and CI builds on this commit succeed; the published package does not. The same include_str! paths are still on main.
Until a packaging fix ships, install from this tag (a git/workspace build, not the crates.io tarball):
cargo install --git https://github.com/Hedronite/rust-tops --tag v0.3.0 cargo-tops --lockedSecurity
rustix1.1.5 → 1.1.6 (direct dependency ofcargo-topsandxtask) to clear RUSTSEC-2026-0486 (unsound zero-length xattr buffer). MSRV stays 1.99.1 (#29).
Added
- Three agent skills,
rust-tops-adopt,rust-tops-gate, andrust-tops-review. Each is aSKILL.mdplus a Nushell script that wrapscargo topsand prints{ok, command, data}.cargo tops init --skillswrites that layout as ordinary files under.agents,.claude,.cursor, and.grok(no symlinks) (#13). - Class profiles as data:
library-util,ffi-bridge, andworkspace-root, merged over the template.initwrites the chosen class profile as data, andcheckrefuses a crate that has none (#17). xtask syncwrites and checks the hand copies listed incopies.toml.initrefuses a symlinkedmain.bend(#19).- The kit CI run of
cargo tops gatein the drop-in, so an adopting tree can take the same gate the kit uses (#18). - A BeautifulRust v1.5.0 strict lint table as the style companion for the kit, with the MIT terms noticed and the lint table marked as adapted. The BeautifulRust MIT text ships in the
cargo-topspackage (#25). docs/REVIEW.md, the review gate. It does not change CRAP, coverage, or mutation.
Changed
cargo topsandcargo-topsare the same binary. Cargo passestopsas the first argument; the binary drops that word before clap parses.- Gate layers are judged as argv steps. An enabled layer with no command is
NotRunand fails the gate. A missingorigin/mainis an empty mutation diff, reported as such (#15, #16). - One coverage run is the test run of unit, integration, and property tests. CRAP is wired only to a fresh lcov file from a coverage run that passed (#20).
- The workspace MSRV,
rust-version, andrust-toolchain.tomlchannel are 1.99.1. cargo-crapis pinned to 0.9.0 and torust-tops.lock, with parent directories held open around the report path (#22).- The kit and drop-in workflows pin
taiki-e/install-actionto v2.88.1, with no fallback install ofcargo-crap(#23). The opt-in fuzz job installscargo-fuzzwith Cargo and pins its actions (#24). RemainingSwatinem/rust-cachesteps are pinned to v2.9.3 (#26, #27). unwrapandexpectare denied outside tests in the kit modules. The strict lint table names its pedantic lints instead of enabling the whole group.
Fixed
- Report-directory handling reuses one
cargo metadataanswer, writes lcov and CRAP under that directory, and creates parent directories before looking for them (#21).
Docs
- Adoption floor for a multi-crate workspace (#14).
- README reflects the v0.2.0 tag, release, and crates.io publish (#12).
Pull requests since v0.2.0
#12, #13, #14, #15, #16, #17, #18, #19, #20, #21, #22, #23, #24, #25, #26, #27, #28, #29.
MSRV
Building cargo-tops needs Rust 1.99.1, the same tool MSRV as 0.2.0.
Full changelog: https://github.com/Hedronite/rust-tops/blob/v0.3.0/CHANGELOG.md
Compare: v0.2.0...v0.3.0