Badgers v2.0.0
Breaking change: bring your own LCOV
Badgers v2 replaces the Python and Flutter-specific collectors with a single tool-agnostic LCOV contract. Your coverage-command must now run tests and write the LCOV file consumed by Badgers. The default input is coverage/lcov.info; override it with lcov-file.
GitHub Action migration
- uses: devgony/badgers@v2
with:
coverage-command: >-
python -m coverage run -m pytest &&
mkdir -p coverage &&
python -m coverage lcov -o coverage/lcov.info
lcov-file: coverage/lcov.infoRust, Python, and Flutter examples are included in examples/workflows/. See the complete v2 migration guide.
CLI migration
badgers collect python→badgers collect lcovbadgers collect flutter→badgers collect lcovbadgers collect lcovreadscoverage/lcov.infoby default and accepts--lcov-file <PATH>
Why this changed
Coverage generation belongs to each ecosystem. Badgers now acts only as the language-independent bridge from an LCOV report to snapshots, merge-base baselines, diff coverage, durable storage, PR comments, Check annotations, and coverage gates.
Full Changelog: v1.3.0...v2.0.0