v2.9.3

Fixes adaptive timeout and coverage setup failures.

• Adaptive baselines now bypass the Go test cache.
• Failed coverage runs stop clearly instead of using partial data.
• -count=0 is rejected with adaptive timeouts.

v2.9.2

Fixes four bugs found by rigorous bug-hunting.

• // mutator-disable-regexp now works on the last line of a file that has no trailing newline.
• The std target now finds standard-library packages again (it looked in a folder removed in Go 1.4).
• Coverage checks no longer pick the wrong file when two file paths share an ending, so results are the same every run.
• The --git-diff-lines filter has the same fix for shared file-name endings.

Each fix has a regression test. Full details in the CHANGELOG.

v2.9.1

Restores fast mutation discovery by batching target package loading. The 14-package dry run is about 9x faster than v2.9.0.

v2.9.0

Speeds up mutation runs by reusing package, coverage, test-binary, source, and report work. Also fixes custom command timeouts and excludes benchmarks from per-test coverage.

v2.8.6

Speeds up package parsing by avoiding full syntax and type loading for dependencies. Warm full-tree dry runs are about five times faster while target-package type information stays available.

v2.8.5

Improves mutation runs that use coverage and adaptive timeouts. They now reuse the coverage test run, avoiding an extra clean test run for each package.

v2.8.4

This release prevents invalid Go syntax when numeric mutations become negative.

Fixed

• numbers/decrementer now wraps negative integer and float mutations in parentheses, avoiding expressions such as value--0.5.

v2.8.3

This release stops --coverage from running tests on uncovered mutants.

Fixed

• --coverage now skips test execution for mutants on uncovered lines. Before, every mutant ran tests first and uncovered ones were thrown away after.

v2.8.2

This release fixes a crash in the agentic JSON report.

Fixed

• The agentic report no longer crashes when a mutant's line number doesn't match its saved source code. This could happen if the two got out of sync.

v2.8.1

This release fixes --test-flags so they apply during the first coverage run.

Fixed

• --coverage now honors --test-flags (for example -short). Before, those flags skipped the coverage step and could mark mutants as not covered.