[meta] prepare releases

Author: sunshowers

nextest-metadata/src/test_list.rs

@@ -122,7 +122,7 @@ impl ListCommand {
     }
 }
 
-/// Root element for a serializable list ofe tests generated by nextest.
+/// Root element for a serializable list of tests generated by nextest.
 #[derive(Clone, Debug, Eq, PartialEq, Deserialize, Serialize)]
 #[serde(rename_all = "kebab-case")]
 #[non_exhaustive]

site/src/changelog.md

@@ -9,13 +9,13 @@ toc_depth: 1
 This page documents new features and bugfixes for cargo-nextest. Please see the [stability
 policy](https://nexte.st/docs/stability/) for how versioning works with cargo-nextest.
 
-## Unreleased
+## [0.9.112] - 2025-11-16
 
 ### Added
 
-- Nextest now supports running tests under a debugger! Use `--debugger` to run a single test under gdb, lldb, WinDbg, CodeLLDB in Visual Studio Code, and other debuggers. For more information, see [_Debugger integration_](https://nexte.st/docs/integrations/debuggers/).
+- Nextest now supports running tests [under a debugger](https://nexte.st/docs/integrations/debuggers/). Use `--debugger` to run a single test under gdb, lldb, WinDbg, CodeLLDB in Visual Studio Code, and other debuggers, while preserving all the environment setup done by nextest.
 
-### Changed
+  Nextest's debugger support will likely see some iteration and improvements over time. If it's missing a feature, please [open a feature request](https://github.com/nextest-rs/nextest/discussions/new?category=feature-requests), or even better, [send a pull request](https://github.com/nextest-rs/nextest/pulls)!
 
 - Nextest now sets [`NEXTEST_BIN_EXE_*` environment variables](https://nexte.st/docs/configuration/env-vars/#environment-variables-nextest-sets) with hyphens in binary names replaced by underscores, in addition to the existing variables with hyphens. This works around some shells and debuggers that drop environment variables containing hyphens. ([#2777])
 
@@ -1660,6 +1660,7 @@ Supported in this initial release:
 - [Test retries](https://nexte.st/book/retries.md) and flaky test detection
 - [JUnit support](https://nexte.st/book/junit.md) for integration with other test tooling
 
+[0.9.112]: https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.112
 [0.9.111]: https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.111
 [0.9.110]: https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.110
 [0.9.109]: https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.109

site/src/docs/ci-features/archiving.md

@@ -202,6 +202,8 @@ Some tests may need to be modified to handle changes in the workspace and target
 
 - To obtain the path to a crate's executables, Cargo provides the [`CARGO_BIN_EXE_<name>`] option to integration tests at build time. To handle target directory remapping, use the value of `NEXTEST_BIN_EXE_<name>` at runtime.
 
+  <!-- md:version 0.9.112 --> Because some shells and [debuggers](../integrations/debuggers.md) drop [environment variables with hyphens in their names](https://unix.stackexchange.com/a/23714), nextest also sets `NEXTEST_BIN_EXE_<name>`, where hyphens in the name are replaced with underscores. This form is now recommended.
+
   To retain compatibility with `cargo test`, you can fall back to the value of `CARGO_BIN_EXE_<name>` at build time.
 
 [`CARGO_BIN_EXE_<name>`]: https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates

site/src/docs/integrations/debuggers.md

@@ -24,6 +24,8 @@ In debugger mode, nextest will:
 * Disable output capturing, similar to the `--no-capture` argument.
 * Pass through standard input to the debugger for interactive terminal use.
 
+Debugger mode is intended primarily for interactive use, so some of the specifics of how the environment is set up may be tweaked over time.
+
 ## Examples
 
 Run the test matching `my_test` under [gdb](https://sourceware.org/gdb/), using `rust-gdb`:
@@ -50,7 +52,7 @@ Debugging tests with [CodeLLDB](https://github.com/vadimcn/codelldb) in Visual S
 
 Install the [CodeLLDB extension](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) if you haven't already.
 
-Then, install `codelldb-launch`:
+Then, install [the `codelldb-launch` tool](https://github.com/vadimcn/codelldb/tree/master/src/codelldb-launch):
 
 ```
 cargo install --locked --git https://github.com/vadimcn/codelldb codelldb-launch