chore(deps): update tokio-tracing monorepo (master) #9

Merged
lucas merged 1 commit from renovate/master-tokio-tracing-monorepo into master 2026-11-06 21:41:20 +01:00
Collaborator

This PR contains the following updates:

Package Type Update Change
tracing (source) dependencies patch 0.1.41 → 0.1.44
tracing-subscriber (source) dependencies patch 0.3.19 → 0.3.23

Release Notes

tokio-rs/tracing (tracing)

v0.1.44: tracing 0.1.44

Compare Source

Fixed
Changed
  • tracing-core: updated to 0.1.36 (#​3440)

v0.1.43: tracing 0.1.43

Compare Source

Important

The previous release 0.1.42 was yanked because #​3382 was a breaking change.
See further details in #​3424. This release contains all the changes from that
version, plus a revert for the problematic part of the breaking PR.

Fixed
  • Revert "make valueset macro sanitary" (#​3425)

v0.1.42: tracing 0.1.42

Compare Source

Important

The Span::record_all method has been removed from the documented API. It
was always unsuable via the documented API as it requried a ValueSet which
has no publically documented constructors. The method remains, but should not
be used outside of tracing macros.

Added
  • attributes: Support constant expressions as instrument field names (#​3158)
  • Add record_all! macro for recording multiple values in one call (#​3227)
  • core: Improve code generation at trace points significantly (#​3398)
Changed
  • tracing-core: updated to 0.1.35 (#​3414)
  • tracing-attributes: updated to 0.1.31 (#​3417)
Fixed
  • Fix "name / parent" variant of event! (#​2983)
  • Remove 'r#' prefix from raw identifiers in field names (#​3130)
  • 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)

Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [tracing](https://tokio.rs) ([source](https://github.com/tokio-rs/tracing)) | dependencies | patch | `0.1.41` → `0.1.44` | | [tracing-subscriber](https://tokio.rs) ([source](https://github.com/tokio-rs/tracing)) | dependencies | patch | `0.3.19` → `0.3.23` | --- ### Release Notes <details> <summary>tokio-rs/tracing (tracing)</summary> ### [`v0.1.44`](https://github.com/tokio-rs/tracing/releases/tag/tracing-0.1.44): tracing 0.1.44 [Compare Source](https://github.com/tokio-rs/tracing/compare/tracing-0.1.43...tracing-0.1.44) ##### Fixed - Fix `record_all` panic ([#&#8203;3432]) ##### Changed - `tracing-core`: updated to 0.1.36 ([#&#8203;3440]) [#&#8203;3432]: https://github.com/tokio-rs/tracing/pull/3432 [#&#8203;3440]: https://github.com/tokio-rs/tracing/pull/3440 ### [`v0.1.43`](https://github.com/tokio-rs/tracing/releases/tag/tracing-0.1.43): tracing 0.1.43 [Compare Source](https://github.com/tokio-rs/tracing/compare/tracing-0.1.42...tracing-0.1.43) ##### Important The previous release [0.1.42] was yanked because [#&#8203;3382] was a breaking change. See further details in [#&#8203;3424]. This release contains all the changes from that version, plus a revert for the problematic part of the breaking PR. ##### Fixed - Revert "make `valueset` macro sanitary" ([#&#8203;3425]) [#&#8203;3382]: https://github.com/tokio-rs/tracing/pull/3382 [#&#8203;3424]: https://github.com/tokio-rs/tracing/pull/3424 [#&#8203;3425]: https://github.com/tokio-rs/tracing/pull/3425 [0.1.42]: https://github.com/tokio-rs/tracing/releases/tag/tracing-0.1.42 ### [`v0.1.42`](https://github.com/tokio-rs/tracing/releases/tag/tracing-0.1.42): tracing 0.1.42 [Compare Source](https://github.com/tokio-rs/tracing/compare/tracing-0.1.41...tracing-0.1.42) ##### Important The [`Span::record_all`] method has been removed from the documented API. It was always unsuable via the documented API as it requried a `ValueSet` which has no publically documented constructors. The method remains, but should not be used outside of `tracing` macros. ##### Added - **attributes**: Support constant expressions as instrument field names ([#&#8203;3158]) - Add `record_all!` macro for recording multiple values in one call ([#&#8203;3227]) - **core**: Improve code generation at trace points significantly ([#&#8203;3398]) ##### Changed - `tracing-core`: updated to 0.1.35 ([#&#8203;3414]) - `tracing-attributes`: updated to 0.1.31 ([#&#8203;3417]) ##### Fixed - Fix "name / parent" variant of `event!` ([#&#8203;2983]) - Remove 'r#' prefix from raw identifiers in field names ([#&#8203;3130]) - Fix perf regression when `release_max_level_*` not set ([#&#8203;3373]) - Use imported instead of fully qualified path ([#&#8203;3374]) - Make `valueset` macro sanitary ([#&#8203;3382]) ##### Documented - **core**: Add missing `dyn` keyword in `Visit` documentation code sample ([#&#8203;3387]) [#&#8203;2983]: https://github.com/tokio-rs/tracing/pull/#&#8203;2983 [#&#8203;3130]: https://github.com/tokio-rs/tracing/pull/#&#8203;3130 [#&#8203;3158]: https://github.com/tokio-rs/tracing/pull/#&#8203;3158 [#&#8203;3227]: https://github.com/tokio-rs/tracing/pull/#&#8203;3227 [#&#8203;3373]: https://github.com/tokio-rs/tracing/pull/#&#8203;3373 [#&#8203;3374]: https://github.com/tokio-rs/tracing/pull/#&#8203;3374 [#&#8203;3382]: https://github.com/tokio-rs/tracing/pull/#&#8203;3382 [#&#8203;3387]: https://github.com/tokio-rs/tracing/pull/#&#8203;3387 [#&#8203;3398]: https://github.com/tokio-rs/tracing/pull/#&#8203;3398 [#&#8203;3414]: https://github.com/tokio-rs/tracing/pull/#&#8203;3414 [#&#8203;3417]: https://github.com/tokio-rs/tracing/pull/#&#8203;3417 [`Span::record_all`]: https://docs.rs/tracing/0.1.41/tracing/struct.Span.html#method.record_all </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Berlin) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xOTUuMCIsInVwZGF0ZWRJblZlciI6IjQzLjE5NS4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
chore(deps): update tokio-tracing monorepo
All checks were successful
pr / check (pull_request) Successful in 1m19s
pr / test (pull_request) Successful in 2m1s
pr / image (pull_request) Successful in 8m34s
d9315d658d
lucas requested review from omp-deck 2026-11-06 21:35:39 +01:00
omp-deck approved these changes 2026-11-06 21:36:09 +01:00
omp-deck left a comment

Lockfile-only patch bump; no source changes needed.

  • tracing 0.1.41→0.1.44, tracing-core 0.1.34→0.1.36, tracing-attributes 0.1.30→0.1.31, tracing-subscriber 0.3.19→0.3.23. All within the existing caret ranges in Cargo.toml (tracing = "0.1.41", tracing-subscriber = "0.3.19"), so no manifest edit is required. tracing-error = "0.2.1" depends on tracing-subscriber ^0.3 and resolves unchanged.
  • The yanked 0.1.42 (breaking valueset change) is not what's being pulled in — 0.1.44 contains the revert from 0.1.43 plus the record_all panic fix. Neither record_all nor ValueSet is used anywhere in this tree, so the API churn is a non-event here.
  • Transitive side effects are all cleanup: tracing-subscriber swapped regex for regex-automata, which lets matchers 0.1→0.2 drop the ancient regex-automata 0.1/regex-syntax 0.6 pair, and nu-ansi-term 0.46→0.50.3 replaces winapi/overload with windows-sys 0.61.2 (already in the graph). Net −2 duplicate regex trees and the last winapi 0.3 usage gone.
  • CI on d9315d6 is green on all three jobs (check, test, image).
Lockfile-only patch bump; no source changes needed. - `tracing` 0.1.41→0.1.44, `tracing-core` 0.1.34→0.1.36, `tracing-attributes` 0.1.30→0.1.31, `tracing-subscriber` 0.3.19→0.3.23. All within the existing caret ranges in `Cargo.toml` (`tracing = "0.1.41"`, `tracing-subscriber = "0.3.19"`), so no manifest edit is required. `tracing-error = "0.2.1"` depends on `tracing-subscriber ^0.3` and resolves unchanged. - The yanked 0.1.42 (breaking `valueset` change) is not what's being pulled in — 0.1.44 contains the revert from 0.1.43 plus the `record_all` panic fix. Neither `record_all` nor `ValueSet` is used anywhere in this tree, so the API churn is a non-event here. - Transitive side effects are all cleanup: `tracing-subscriber` swapped `regex` for `regex-automata`, which lets `matchers` 0.1→0.2 drop the ancient `regex-automata 0.1`/`regex-syntax 0.6` pair, and `nu-ansi-term` 0.46→0.50.3 replaces `winapi`/`overload` with `windows-sys 0.61.2` (already in the graph). Net −2 duplicate regex trees and the last `winapi` 0.3 usage gone. - CI on d9315d6 is green on all three jobs (check, test, image).
lucas merged commit 8fc87a31b7 into master 2026-11-06 21:41:20 +01:00
lucas deleted branch renovate/master-tokio-tracing-monorepo 2026-11-06 21:41:21 +01:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
lucas/logview!9
No description provided.