Bump cargo-llvm-cov from 0.6.23 to 0.8.1

[dependabot]

Bumps cargo-llvm-cov from 0.6.23 to 0.8.1.

Release notes

Sourced from cargo-llvm-cov's releases.

0.8.1

• Back "cargo-llvm-cov subcommands other than report and clean may not work correctly ..." error to warning.

  This was changed from a warning to an error in 0.7.0, but it has been reverted because a case where it previously worked without issues was reported.

0.8.0

• Support glob pattern, versioned name with partial version or <name>@<version> syntax, and package spec in --package. Previously, only package name and versioned package name with <name>:<full_version> are supported. (#476)

  This also fixes regression introduced in 0.7.0 where causing packages specified with --package are wrongly excluded from report/test when package is specified with the above syntaxes.

• Support glob pattern, versioned name, and package spec in --exclude. When we tested it previously, Cargo did not support this, but the current version of Cargo does support it. (#476)

• Align the exclusion behavior in reports when cargo-llvm-cov is performed in a sub-crate directory of a workspace or in the root crate of a non-virtual workspace without using --workspace or --package, to match the behavior when --workspace or --package is used (by default, only show the tested crates). (#476)

  Compatibility Note: When --workspace or --package is not used, this will exclude other untested workspace members from the report that were previously implicitly included.

  If you want to test other workspace members, consider using --workspace or --package. If you don't want to test other workspace members but still want to include them in the report, consider using --workspace or --exclude-from-test.

0.7.1

• Fix regression introduced in 0.7.0 where causing coverage test failure in nextest's CI. (6e30e6f)

0.7.0

• Improve compilation time, execution time, and disk usage by applying the flags required for code coverage instrumentation only to the crates that actually need them. (#471)

  Previously, there flags ware applied to the entire dependency graph, but most of it was actually unnecessary. Previous behavior can be opted into with --no-rustc-wrapper.

• Fix a bug where --package option is not correctly handled and other unspecified workspace members are shown in the report. (#473)

• Support coverage for proc-macro and build script even with cross-compilation. (#471)

  Previously, it was only supported when testing against the host target.

• Stabilize --dep-coverage. (#471)

  Several bugs have been fixed, and improvements such as supporting multiple crates have also been made.

• Stabilize --disable-default-ignore-filename-regex as --no-default-ignore-filename-regex. (8db80d5)

  The old name is still available as an alias, but may removed in future breaking release.

• cargo llvm-cov show-env improvements:

  • Add --cmd and --fish. (#472)

  • Rename --export-prefix to --sh, --with-pwsh-env-prefix to --pwsh for consistency and clarity. (#472)

    The old names are still available as aliases, but may removed in future breaking release.

• Turn some warnings into hard error. (837a118)

• Diagnostics improvements. (93840f8)

... (truncated)

Changelog

Sourced from cargo-llvm-cov's changelog.

[0.8.1] - 2026-01-26

• Back "cargo-llvm-cov subcommands other than report and clean may not work correctly ..." error to warning.

  This was changed from a warning to an error in 0.7.0, but it has been reverted because a case where it previously worked without issues was reported.

[0.8.0] - 2026-01-26

• Support glob pattern, versioned name with partial version or <name>@<version> syntax, and package spec in --package. Previously, only package name and versioned package name with <name>:<full_version> are supported. (#476)

  This also fixes regression introduced in 0.7.0 where causing packages specified with --package are wrongly excluded from report/test when package is specified with the above syntaxes.

• Support glob pattern, versioned name, and package spec in --exclude. When we tested it previously, Cargo did not support this, but the current version of Cargo does support it. (#476)

• Align the exclusion behavior in reports when cargo-llvm-cov is performed in a sub-crate directory of a workspace or in the root crate of a non-virtual workspace without using --workspace or --package, to match the behavior when --workspace or --package is used (by default, only show the tested crates). (#476)

  Compatibility Note: When --workspace or --package is not used, this will exclude other untested workspace members from the report that were previously implicitly included.

  If you want to test other workspace members, consider using --workspace or --package. If you don't want to test other workspace members but still want to include them in the report, consider using --workspace or --exclude-from-test.

[0.7.1] - 2026-01-24

• Fix regression introduced in 0.7.0 where causing coverage test failure in nextest's CI. (6e30e6f)

[0.7.0] - 2026-01-24

• Improve compilation time, execution time, and disk usage by applying the flags required for code coverage instrumentation only to the crates that actually need them. (#471)

  Previously, there flags ware applied to the entire dependency graph, but most of it was actually unnecessary. Previous behavior can be opted into with --no-rustc-wrapper.

• Fix a bug where --package option is not correctly handled and other unspecified workspace members are shown in the report. (#473)

• Support coverage for proc-macro and build script even with cross-compilation. (#471)

  Previously, it was only supported when testing against the host target.

• Stabilize --dep-coverage. (#471)

  Several bugs have been fixed, and improvements such as supporting multiple crates have also been made.

• Stabilize --disable-default-ignore-filename-regex as --no-default-ignore-filename-regex. (8db80d5)

  The old name is still available as an alias, but may removed in future breaking release.

• cargo llvm-cov show-env improvements:

  • Add --cmd and --fish. (#472)

  • Rename --export-prefix to --sh, --with-pwsh-env-prefix to --pwsh for consistency and clarity. (#472)

    The old names are still available as aliases, but may removed in future breaking release.

... (truncated)

Commits

• a8e590c Release 0.8.1
• 8352850 Back "cargo-llvm-cov subcommands other than report and clean may not work cor...
• 9ffb15e Release 0.8.0
• f44ab08 Rework WorkspaceMembers::new
• eac9449 Release 0.7.1
• 4cd3d3f Update changelog
• 6e30e6f Fix regression causing coverage test failure in nextest's CI
• 822bf6c Release 0.7.0
• 539c796 Update changelog
• 254e541 metadata: Turn PackageId into index
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)