Releases: taiki-e/cargo-llvm-cov
0.2.0
-
Update to stabilized
-C instrument-coverage
. (#130)Support for
-Z instrument-coverage
in the old nightly will also be kept for compatibility.Compatibility Note: In 0.2, if
-C instrument-coverage
or-Z instrument-coverage
is not available in the default toolchain, runningcargo llvm-cov
will find and use nightly (this is almost the same behavior as 0.1). This behavior is necessary because only the recent nightly currently supports-C instrument-coverage
(and also for compatibility with 0.1). This behavior will be changed in 0.3 to always select the default toolchain. If you are likely to be affected by the change in 0.3, cargo-llvm-cov will emit a warning. 0.3 is planned to be released after-C instrument-coverage
is available in the stable toolchain. -
Remove support of multiple values in
--package
and--exclude
. (#133) -
Add
--exclude-from-test
option to exclude specific packages from the test but not from the report. (#131) -
Add
--exclude-from-report
option to exclude specific packages from the report but not from the test. (#131) -
Workspace members are now always included in the report unless specified by
--exclude
or--exclude-from-report
. (#131)
0.1.16
-
Alleviate an issue where "File name or extension is too long" error occurs in Windows. (#126, thanks @aganders3)
-
Re-enable multiple values for
--package
and--exclude
. (#127, thanks @aganders3)This behavior was unintentionally enabled in older versions and disabled in recent versions.
We will support this again in 0.1.x for compatibility, but will remove it in 0.2.x.
-
Distribute prebuilt binaries for aarch64 Linux (gnu and musl).
0.1.15
0.1.14
-
Add
show-env
subcommand. (#115, thanks @davidhewitt) -
cargo-llvm-cov no longer sets
CARGO_TARGET_DIR
. (#112, thanks @smoelius) -
cargo-llvm-cov can now properly exclude arbitrary
CARGO_HOME
andRUSTUP_HOME
from reports.
0.1.13
0.1.12
0.1.11
- Fix "conflicting weak extern definition" error on windows. (#101)
0.1.10
0.1.9
0.1.8
- Fix an issue where some files were incorrectly ignored in reports. (#94, thanks @larsluthman)