nextest-runner 0.59.0

See the changelog for cargo-nextest 0.9.76.

nextest-metadata 0.11.3

Changed

• NextestExitCode::INVALID_FILTER_EXPRESSION has been renamed to
  NextestExitCode::INVALID_FILTERSET. The old name is kept around as a deprecated alias -- it will
  be removed in the next major version.

nextest-filtering 0.11.0

Changed

• Types renamed from FilteringExpr to Filterset.

cargo-nextest 0.9.76

Added

• A new --bound=all option disables the default set on the command line.
• --run-ignored ignored-only has been shortened to --run-ignored only. (The old name still works
  as an alias.)

Fixed

• Documentation links updated to point to the new website.

Changed

• Previously, passing in any -E options would disable the default set. However in practice that
  was found to be too confusing, and this behavior has been removed. Instead, use --bound.

  This is technically a breaking change, but default sets aren't in wide use yet so this should have
  minimal impact.

nextest-runner 0.58.0

See the changelog for cargo-nextest 0.9.75.

nextest-metadata 0.11.2

Added

• New exit code NO_TESTS_RUN = 4, indicating no tests to run.
• Support for a new mismatch reason for tests and binaries: that they are not in the default set.

nextest-metadata 0.11.1

Added

• New exit code NO_TESTS_RUN = 4, indicating no tests to run.
• Support for a new mismatch reason for tests and binaries: that they are not in the default set.

nextest-filtering 0.10.0

Added

• New APIs: CompiledExpr::matches_binary and matches_test.
• Support for parsing default sets and the default() predicate.

Changed

• FilteringExpr::parse now takes a ParseContext.
• The matches_binary and matches_test functions now take an EvalContext.
• MSRV updated to Rust 1.75.

cargo-nextest 0.9.75

Added

• Support for default sets of tests to run via the default-set configuration. See Running a
  subset of tests by default
  for more information.
• A new --no-tests option controls the behavior of nextest when no tests are run. The possible
  values are pass, warn and fail. Per the behavior changed described in discussion
  #1646, the current default is warn, and
  it will change to fail in the future.

nextest-runner 0.57.0

See the changelog for cargo-nextest 0.9.73.