nextest-rs/nextest (cargo-nextest)
### [`v0.9.78`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.78): cargo-nextest 0.9.78
[Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.77...cargo-nextest-0.9.78)
##### Added
For failing tests, if nextest finds text matching patterns that indicate failure, such as "thread
panicked at", it now highlights those lines (if color is enabled).
Rust's libtest doesn't provide structured output for this, so nextest uses heuristics. These
heuristics will be tweaked over time; to see what nextest would highlight, run `cargo nextest debug
extract highlight`, and provide either `--stdout` and `--stderr`, or `--combined` if stdout and
stderr are combined.
### [`v0.9.77`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.77): cargo-nextest 0.9.77
[Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.76...cargo-nextest-0.9.77)
##### Changed
A couple of UI changes:
- `default-set` is now `default-filter`.
- `--bound=all` is now `--ignore-default-filter`.
Sorry about the breakage here -- this should be the last of the changes.
### [`v0.9.76`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.76): cargo-nextest 0.9.76
[Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.75...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.
### [`v0.9.75`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.75): cargo-nextest 0.9.75
[Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.74...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*](https://nexte.st/docs/running#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](https://redirect.github.com/nextest-rs/nextest/discussions/1646), the current default is `warn`, and
it will change to `fail` in the future.
### [`v0.9.74`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.74): cargo-nextest 0.9.74
[Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.72...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](https://redirect.github.com/nextest-rs/nextest/discussions/1646) for more.
### [`v0.9.72`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.72): cargo-nextest 0.9.72
[Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.70...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](https://redirect.github.com/nextest-rs/nextest/issues/267) and [#1493](https://redirect.github.com/nextest-rs/nextest/issues/1493) for more details.
Thanks to [06393993](https://redirect.github.com/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](https://redirect.github.com/nextest-rs/nextest/issues/1515).)
Configuration
📅 Schedule: Branch creation - "after 8pm,before 6am" in timezone America/Denver, Automerge - "after 8pm,before 6am" in timezone America/Denver.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
0.9.70->0.9.78Release Notes
nextest-rs/nextest (cargo-nextest)
### [`v0.9.78`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.78): cargo-nextest 0.9.78 [Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.77...cargo-nextest-0.9.78) ##### Added For failing tests, if nextest finds text matching patterns that indicate failure, such as "thread panicked at", it now highlights those lines (if color is enabled). Rust's libtest doesn't provide structured output for this, so nextest uses heuristics. These heuristics will be tweaked over time; to see what nextest would highlight, run `cargo nextest debug extract highlight`, and provide either `--stdout` and `--stderr`, or `--combined` if stdout and stderr are combined. ### [`v0.9.77`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.77): cargo-nextest 0.9.77 [Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.76...cargo-nextest-0.9.77) ##### Changed A couple of UI changes: - `default-set` is now `default-filter`. - `--bound=all` is now `--ignore-default-filter`. Sorry about the breakage here -- this should be the last of the changes. ### [`v0.9.76`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.76): cargo-nextest 0.9.76 [Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.75...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. ### [`v0.9.75`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.75): cargo-nextest 0.9.75 [Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.74...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*](https://nexte.st/docs/running#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](https://redirect.github.com/nextest-rs/nextest/discussions/1646), the current default is `warn`, and it will change to `fail` in the future. ### [`v0.9.74`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.74): cargo-nextest 0.9.74 [Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.72...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](https://redirect.github.com/nextest-rs/nextest/discussions/1646) for more. ### [`v0.9.72`](https://redirect.github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.72): cargo-nextest 0.9.72 [Compare Source](https://redirect.github.com/nextest-rs/nextest/compare/cargo-nextest-0.9.70...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](https://redirect.github.com/nextest-rs/nextest/issues/267) and [#1493](https://redirect.github.com/nextest-rs/nextest/issues/1493) for more details. Thanks to [06393993](https://redirect.github.com/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](https://redirect.github.com/nextest-rs/nextest/issues/1515).)Configuration
📅 Schedule: Branch creation - "after 8pm,before 6am" in timezone America/Denver, Automerge - "after 8pm,before 6am" in timezone America/Denver.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.