chore: prepare tracing 0.1.42

# 0.1.42 (November 30, 2025)

### Added

- **attributes**: Support constant expressions as instrument field names ([#3158])
- **core**: Improve code generation at trace points significantly ([#3398])

### Fixed

- Fix perf regression when `release_max_level_*` not set ([#3373])
- Use imported instead of fully qualified path ([#3374])
- Make `valueset` macro sanitary ([#3382])

### Documented

- **core**: Add missing `dyn` keyword in `Visit` documentation code sample ([#3387])

[#3158]: https://github.com/tokio-rs/tracing/pull/#3158
[#3373]: https://github.com/tokio-rs/tracing/pull/#3373
[#3374]: https://github.com/tokio-rs/tracing/pull/#3374
[#3382]: https://github.com/tokio-rs/tracing/pull/#3382
[#3387]: https://github.com/tokio-rs/tracing/pull/#3387
[#3398]: https://github.com/tokio-rs/tracing/pull/#3398

Author: hds

tracing/CHANGELOG.md

@@ -1,3 +1,27 @@
+# 0.1.42 (November 30, 2025)
+
+### Added
+
+- **attributes**: Support constant expressions as instrument field names ([#3158])
+- **core**: Improve code generation at trace points significantly ([#3398])
+
+### Fixed
+
+- Fix perf regression when `release_max_level_*` not set ([#3373])
+- Use imported instead of fully qualified path ([#3374])
+- Make `valueset` macro sanitary ([#3382])
+
+### Documented
+
+- **core**: Add missing `dyn` keyword in `Visit` documentation code sample ([#3387])
+
+[#3158]: https://github.com/tokio-rs/tracing/pull/#3158
+[#3373]: https://github.com/tokio-rs/tracing/pull/#3373
+[#3374]: https://github.com/tokio-rs/tracing/pull/#3374
+[#3382]: https://github.com/tokio-rs/tracing/pull/#3382
+[#3387]: https://github.com/tokio-rs/tracing/pull/#3387
+[#3398]: https://github.com/tokio-rs/tracing/pull/#3398
+
 # 0.1.41 (November 27, 2024)
 
 [ [crates.io][crate-0.1.41] ] | [ [docs.rs][docs-0.1.41] ]

tracing/Cargo.toml

@@ -5,7 +5,7 @@ name = "tracing"
 # - Update doc url in README.md.
 # - Update CHANGELOG.md.
 # - Create "tracing-0.1.x" git tag
-version = "0.1.41"
+version = "0.1.42"
 authors = ["Eliza Weisman <[email protected]>", "Tokio Contributors <[email protected]>"]
 license = "MIT"
 readme = "README.md"

tracing/README.md

@@ -16,9 +16,9 @@ Application-level tracing for Rust.
 [Documentation][docs-url] | [Chat][discord-url]
 
 [crates-badge]: https://img.shields.io/crates/v/tracing.svg
-[crates-url]: https://crates.io/crates/tracing
+[crates-url]: https://crates.io/crates/tracing/0.1.42
 [docs-badge]: https://docs.rs/tracing/badge.svg
-[docs-url]: https://docs.rs/tracing
+[docs-url]: https://docs.rs/tracing/0.1.42
 [docs-v0.2.x-badge]: https://img.shields.io/badge/docs-v0.2.x-blue
 [docs-v0.2.x-url]: https://tracing.rs/tracing
 [mit-badge]: https://img.shields.io/badge/license-MIT-blue.svg
@@ -250,7 +250,7 @@ my_future
 is as long as the future's.
 
 The second, and preferred, option is through the
-[`#[instrument]`](https://docs.rs/tracing/0.1.41/tracing/attr.instrument.html)
+[`#[instrument]`](https://docs.rs/tracing/0.1.42/tracing/attr.instrument.html)
 attribute:
 
 ```rust
@@ -297,7 +297,7 @@ span.in_scope(|| {
 // Dropping the span will close it, indicating that it has ended.
 ```
 
-The [`#[instrument]`](https://docs.rs/tracing/0.1.41/tracing/attr.instrument.html) attribute macro
+The [`#[instrument]`](https://docs.rs/tracing/0.1.42/tracing/attr.instrument.html) attribute macro
 can reduce some of this boilerplate:
 
 ```rust