[nextest] prepare for releases

nextest-rs · Feb 24, 2022 · 4fd59e0 · 4fd59e0
1 parent 0d2c05b
commit 4fd59e0
Show file tree

Hide file tree

Showing 7 changed files with 31 additions and 7 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/cargo-nextest/Cargo.toml b/cargo-nextest/Cargo.toml
@@ -1,7 +1,7 @@
 [package]
 name = "cargo-nextest"
 description = "A next-generation test runner for Rust."
-version = "0.9.7"
+version = "0.9.8"
 readme = "README.md"
 license = "Apache-2.0 OR MIT"
 repository = "https://github.com/nextest-rs/nextest"
@@ -23,7 +23,7 @@ enable-ansi-support = "0.1.2"
 env_logger = { version = "0.9.0", default-features = false }
 guppy = "0.13.0"
 log = "0.4.14"
-nextest-runner = { version = "0.2.1", path = "../nextest-runner" }
+nextest-runner = { version = "0.3.0", path = "../nextest-runner" }
 nextest-metadata = { version = "0.1.0", path = "../nextest-metadata" }
 owo-colors = { version = "3.2.0", features = ["supports-colors"] }
 shellwords = "1.1.0"

diff --git a/nextest-runner/CHANGELOG.md b/nextest-runner/CHANGELOG.md
@@ -1,5 +1,15 @@
 # Changelog
 
+## [0.3.0] - 2022-02-23
+
+### Fixed
+
+- Target runners of the form `runner = ["bin-name", "--arg1", ...]` are now parsed correctly ([#75]).
+- Binary IDs for `[[bin]]` and `[[example]]` tests are now unique, in the format `<crate-name>::bin/<binary-name>` and `<crate-name>::test/<binary-name>` respectively ([#76]).
+
+[#75]: https://github.com/nextest-rs/nextest/pull/75
+[#76]: https://github.com/nextest-rs/nextest/pull/76
+
 ## [0.2.1] - 2022-02-23
 
 - Improvements to `TargetRunnerError` message display: source errors are no longer displayed directly, only in "caused by".
@@ -28,6 +38,7 @@
 
 - Initial version.
 
+[0.3.0]: https://github.com/nextest-rs/nextest/releases/tag/nextest-runner-0.3.0
 [0.2.1]: https://github.com/nextest-rs/nextest/releases/tag/nextest-runner-0.2.1
 [0.2.0]: https://github.com/nextest-rs/nextest/releases/tag/nextest-runner-0.2.0
 [0.1.2]: https://github.com/nextest-rs/nextest/releases/tag/nextest-runner-0.1.2

diff --git a/nextest-runner/Cargo.toml b/nextest-runner/Cargo.toml
@@ -1,7 +1,7 @@
 [package]
 name = "nextest-runner"
 description = "Core runner logic for cargo nextest."
-version = "0.2.1"
+version = "0.3.0"
 readme = "README.md"
 license = "MIT OR Apache-2.0"
 repository = "https://github.com/nextest-rs/nextest"

diff --git a/site/src/CHANGELOG.md b/site/src/CHANGELOG.md
@@ -3,6 +3,16 @@
 This page documents new features and bugfixes for cargo-nextest. Please see the [stability
 policy](book/stability.md) for how versioning works with cargo-nextest.
 
+## [0.9.8] - 2022-02-23
+
+### Fixed
+
+- Target runners of the form `runner = ["bin-name", "--arg1", ...]` are now parsed correctly ([#75]).
+- Binary IDs for `[[bin]]` and `[[example]]` tests are now unique, in the format `<crate-name>::bin/<binary-name>` and `<crate-name>::test/<binary-name>` respectively ([#76]).
+
+[#75]: https://github.com/nextest-rs/nextest/pull/75
+[#76]: https://github.com/nextest-rs/nextest/pull/76
+
 ## [0.9.7] - 2022-02-23
 
 ### Fixed
@@ -80,6 +90,7 @@ Supported in this initial release:
 * [Test retries](book/retries.md) and flaky test detection
 * [JUnit support](book/junit.md) for integration with other test tooling
 
+[0.9.8]: https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.8
 [0.9.7]: https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.7
 [0.9.6]: https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.6
 [0.9.5]: https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.5

diff --git a/site/src/book/running.md b/site/src/book/running.md
@@ -14,7 +14,7 @@ In the output above:
 * Tests are marked **`PASS`** or **`FAIL`**, and the amount of wall-clock time each test takes is listed within square brackets. In the example above, **`test_list_tests`** passed and took 0.603 seconds to execute.
 * The part of the test in purple is the *test binary*. A test binary is either:
   * a *unit test binary* built from tests inline within `lib.rs`. These test binaries are shown by nextest as just the crate name, without a `::` separator inside them.
-  * an *integration test binary* built from tests in the `[[test]]` section of `Cargo.toml` (typically tests in the `tests` directory.) These tests are shown by nextest in the format `crate-name::bin-name`.
+  * an *integration test binary* built from tests in the `[[test]]` section of `Cargo.toml` (typically tests in the `tests` directory.) These tests are shown by nextest in the format `crate-name::bin-name`[^bin-example].
 
   For more about unit and integration tests, see [the documentation for `cargo test`](https://doc.rust-lang.org/cargo/commands/cargo-test.html).
 * The part after the test binary is the *test name*, including the module the test is in. The final part of the test name is highlighted in bold blue text.
@@ -27,6 +27,8 @@ cargo nextest run -p my-package
 
 For a full list of options accepted by `cargo nextest run`, see `cargo nextest run --help`.
 
+[^bin-example]: `bin` and `example` targets can also contain tests. Those are represented as `crate-name::bin/bin-name` and `crate-name::example/example-name`, respectively.
+
 ### Filtering tests
 
 To only run tests that match certain names:

diff --git a/site/src/book/stability.md b/site/src/book/stability.md
@@ -15,7 +15,7 @@ The public API does *not* include human-readable output generated by nextest, or
 
 ## Libraries
 
-The libraries used by cargo-nextest, [nextest-metadata](https://crates.io/crates/nextest-metadata) and [nextest-runner](https://crates.io/crates/nextest-runner), follow the standard Rust library versioning policy.
+The libraries used by cargo-nextest, [nextest-metadata](https://crates.io/crates/nextest-metadata) and [nextest-runner](https://crates.io/crates/nextest-runner), follow the standard Rust library versioning policy. Breaking changes to `nextest-runner` in particular will happen more rapidly than changes to `cargo-nextest`.
 
 ## Minimum supported Rust version (MSRV)