Repository navigation
cargo-cleanme v0.1.2
cargo-cleanme v0.1.2 — qualification release
A deliberately small release. It changes no product behavior; every change is to
test evidence, release reproducibility, and the release record.
Why this version exists: v0.1.1 was both the newest published version and the
first one containing a working updater, so the live self-update path could not be
rehearsed against a real newer release. v0.1.2 makes that rehearsal possible.
Release reproducibility
- The release builder is pinned to one exact Rust release,
1.99.0, on all five
contracted targets. It wasstable, so rebuilding a tag could use a different
compiler.1.99.0is the version that built and qualified v0.1.1, so this
records an already-proven input rather than changing one. This is not an
MSRV change: the declared MSRV remains1.89. - A release tag is now bound to the source identity in the tree — tag version,
Cargo.toml,Cargo.lock, the revision the tag points at, and a changelog
entry must all agree before a release is staged. A stale or mistyped tag
previously resolved cleanly and would have staged a draft whose tag and asset
names disagreed with the version the binary reports.
Test and release evidence
- The release-candidate smoke validator accepted a scan that discovered zero
manifests and ignored diagnostics, so it could report a healthy candidate
while the product's own Cargo integration was failing. It now asserts the exact
manifest count, rejects any Cargo diagnostic, and probes the real Cargo first. - The installer fixture cases for a missing binary, a missing Cargo, and a Cargo
run that produces nothing asserted only a non-zero exit — which a dead fixture
server or an unrelated failure also satisfies. They now assert the wrapper's
own diagnostic. - A case that could not run (an unwritable-directory case running as root) is now
reported as a skip rather thanok, and a host on which no installer block can
run exits non-zero instead of reporting a green run that qualified nothing. - The live self-update rehearsal is a repeatable script, and its five-target
matrix is mechanically checked against the release runners.
Known limitation in this release
An explicitly relative scan root — cargo-cleanme scan some/dir — silently
resolves zero Cargo workspaces and reports no groups, because the relative
manifest path is passed to Cargo with the child's working directory set to that
manifest's own parent. The absolute spelling of the same directory is correct.
The failure direction is fail-safe: a degraded scan reports less reclaimable
space, so clean deletes less, never more. But the result can read as a false
all-clear. Use an absolute path until this is fixed. Tracked as C015.
Install
# direct binary (Linux; `uname -m` is x86_64 or aarch64, which is the triple)
curl -fsSLO https://github.com/dbowm91/cargo-cleanme/releases/download/v0.1.2/cargo-cleanme-$(uname -m)-unknown-linux-gnu
sha256sum -c cargo-cleanme-$(uname -m)-unknown-linux-gnu.sha256
# or from source
cargo install cargo-cleanme --lockedPublic installers: install.sh (Linux/macOS) and install.ps1 (Windows) are
attached to this release and verify the .sha256 sidecar of every asset before
installing anything.
Verify an asset before trusting it:
sha256sum -c cargo-cleanme-<target>.sha256