nextest-runner 0.57.0

See the changelog for cargo-nextest 0.9.73.

cargo-nextest 0.9.74

Added

Warnings are now printed in the following cases:

• If some tests are not run, e.g. due to --fail-fast.
• If no tests are run.

Changed

• Updated MSRV for compiling nextest to Rust 1.75.

Upcoming behavior changes

If no tests are run, nextest will start exiting with the advisory code 4 in versions released after 2024-11-18. See discussion #1646 for more.

cargo-nextest 0.9.74-rc.1

Added

Warnings are now printed in the following cases:

• If some tests are not run, e.g. due to --fail-fast.
• If no tests are run.

Changed

• Updated MSRV for compiling nextest to Rust 1.75.

Upcoming behavior changes

If no tests are run, nextest will start exiting with the advisory code 4 in versions released after 2024-11-18. See discussion #1646 for more.

nextest-runner 0.56.1

See the changelog for cargo-nextest 0.9.72.

nextest-runner 0.56.0

See the changelog for cargo-nextest 0.9.71.

nextest-metadata 0.11.0

Added

• RustBuildMetaSummary now has a new platforms field, which contains information about host and
  target platforms. This field is provided by cargo-nextest 0.9.71 and above.

Changed

• MSRV updated to Rust 1.73.
• RustBuildMetaSummary::target_platforms is now deprecated -- use
  RustBuildMetaSummary::platforms if available.

nextest-filtering 0.9.0

Changed

• MSRV updated to Rust 1.74.
• nextest-metadata updated to 0.11.0.

cargo-nextest 0.9.72

Fixed

Previously, nextest would be unable to run proc-macro tests in some circumstances:

• On Windows, with rustup 1.27.2 and above
• On all platforms, if cargo is used without rustup, or if the cargo-nextest binary is invoked directly

With this release, proc-macros tests now work in all circumstances. This is done by nextest detecting Rust libdirs for the host and target platforms, and adding them to the library path automatically.

(There's also the less-common case of test binaries compiled with -C prefer-dynamic. These
situations now also work.)

See #267 and #1493 for more details.

Thanks to 06393993 for your first contribution!

Changed

As part of the above fix, libstd is now included in all archives. This makes archives around 4MB bigger, or around 8MB in cross-compilation scenarios. (It is possible to address this via config knobs -- if this is particularly bothersome to you, please post in #1515.)

cargo-nextest 0.9.71

Fixed

Previously, nextest would be unable to run proc-macro tests in some circumstances:

• On Windows, with rustup 1.27.2 and above
• On all platforms, if cargo is used without rustup, or if the cargo-nextest binary is invoked directly

With this release, proc-macros tests now work in all circumstances. This is done by nextest detecting Rust libdirs for the host and target platforms, and adding them to the library path automatically.

(There's also the less-common case of test binaries compiled with -C prefer-dynamic. These
situations now also work.)

See #267 and #1493 for more details.

Thanks to 06393993 for your first contribution!

Changed

As part of the above fix, libstd is now included in all archives. This makes archives around 4MB bigger, or around 8MB in cross-compilation scenarios. (It is possible to address this via config knobs -- if this is particularly bothersome to you, please post in #1515.)

nextest-runner 0.55.0

See the changelog for cargo-nextest 0.9.69.