v1.3.4

cargo-hold v1.3.4

v1.3.4 fixes a cargo hold voyage cache correctness issue when restored target artifacts are stale and source files have changed. voyage now leaves artifact mtimes alone in changed-source runs so the next Cargo build can correctly rebuild instead of seeing refreshed artifacts as current.

Full Changelog: v1.3.3...v1.3.4

Breaking Changes

• None.

Highlights Since v1.3.3

Voyage Cache Correctness

• cargo hold voyage now uses the anchor/salvage source-change report to detect modified or newly added tracked files before garbage collection.
• When source changes are present, the heave phase skips artifact mtime rejuvenation for restored build artifacts.
• Standalone cargo hold heave and no-change voyage runs keep the existing artifact preservation behavior.
• Added regression coverage for stale artifact mtimes after a source change.

Upgrade Notes

• No migration is required.
• Upgrading is recommended for CI jobs that restore a target cache and run cargo hold voyage before building.

Pull Requests by Category

Bug Fixes

• fix: skip voyage artifact rejuvenation after source changes (#72)

Misc

• chore: bump version (#70)