Added
- Push README to DockerHub as overview
Added
--skip-coverage-pathregex option to exclude matching paths from uncovered line calculations and list skipped paths in the summary output- cargo fmt to GitHub workflow
Changed
- CLI output lines order
Fixed
- Bump version in Cargo.toml
Changed
- Change entrypoint to cmd to simplify CI usage
Fixed
- dockerhub release
Fixed
- Fix Docker releases
Changed
- Output binaries as archives in releases
- Dockerhub AND GHCR release
Added
- Dockerhub release
Changed
- Output binaries in releases instead of archives with README
Fixed
- Invalid version in Cargo.toml
Fixed
- Fix coverage of files with the same name in different directories
Added
- Add auto publishing to crates.io
Fixes
- Fix GitHub Actions release matrix targets - install Cross
Fixes
- Fix GitHub Actions release matrix targets (remove stray trailing commas) so macOS builds resolve the correct Rust target.
We're excited to ship the very first release of diff-coverage, a developer‑focused CLI that makes coverage on changed code fast, reliable, and CI‑friendly. Built for teams who want actionable coverage signals without slow or unreliable pipelines.
What's new
- Blazing‑fast runs: up to ~108× faster mean wall‑time vs Python diff‑cover in larger runs
- Memory‑efficient processing: ~21–28× lower peak RSS memory usage
- Coverage directories supported: point to directories (not just single files) for flexible CI setups
--fail-undersupport: enforce quality gates directly in your pipeline
Why it matters diff-coverage is designed for modern dev workflows—fast enough for tight inner loops, strict enough for CI, and predictable across mono‑repos and multi‑coverage setups.
Thanks for being part of the very first release — more to come!