anodizer0.30.0

Anodizer Release Automation turns a declarative configuration into a complete Rust release through one anodizer release command, handling builds, archives, checksums, changelogs, signing, releases, publishing, and announcements. It treats a Cargo workspace as a connected project rather than a collection of unrelated binaries, so one configuration can serve a single crate or a monorepo with thirty crates. Per-crate release schedules, tags, and tag resolution are supported, while anodizer tag and anodizer bump update Cargo.toml and Cargo.lock before committing and tagging locally; the --push option sends both atomically.

For crates.io publishing, Anodizer determines dependency order and polls the sparse index so dependent crates wait for their prerequisites to become available. It can cross-compile musl, glibc, Windows, and macOS targets from one machine through cargo-zigbuild or cross. Deterministic artifacts are the default, and anodizer check determinism rebuilds and compares them byte-for-byte to verify reproducibility.

Signing covers binaries, archives, checksums, and images through cosign and GPG, with SLSA-style build provenance also available. Rust maintainers can generate per-crate README files, derive cargo-binstall metadata from the configuration, pin documentation and installation scripts with version_files, and run post-release installation smoke tests. GoReleaser users will recognize its {{ .Field }} template syntax.

Published by TJ Smith for Windows in the System Tools category, version 0.30.0 is freeware and suits developers managing Rust release pipelines. Contributions to the project are made through GitHub, which requires creating an account.