v1.3.2
·
5 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
cargo-hold v1.3.2
Patch release focused on making CI cache recovery fail correctly and preserving restored build artifacts during garbage collection. This release also hardens the release pipeline with trusted publishing and binary attestations.
Full Changelog: v1.3.1...v1.3.2
Breaking Changes
None.
Highlights Since v1.3.1
CI Cache Correctness
stowandsalvagenow fail when tracked files cannot be read or hashed, instead of silently writing or restoring partial metadata.heavenow refreshes stale mtimes on recently restored crate artifacts before selecting artifacts for removal, preventing restored CI caches from being immediately deleted.- Timestamp restoration now validates repository-relative metadata paths before applying mtimes.
Release Integrity
- Release binaries are now attested through GitHub artifact attestations.
- Publishing now uses crates.io trusted publishing instead of a long-lived registry token.
Pull Requests by Category
Bug Fixes
- Fix CI failures when
salvage/stowskip files andheaveeats restored cache (#62) - Satisfy
clippy::manual_checked_opsin GC auto-cap sizing (#64)