bitsquid_dt/dtmt
bitsquid_dt/dtmt
2
Fork 0
Code Issues 35 Pull requests 9 Projects 1 Releases 3 Packages 1 Wiki Activity Actions

fix(deps): update tokio-tracing monorepo #319

Open
renovate-bot wants to merge 1 commit from renovate/tokio-tracing-monorepo into master
pull from: renovate/tokio-tracing-monorepo
merge into: bitsquid_dt:master
Conversation 0 Commits 1 Files changed 1 +14 -14
renovate-bot bot commented 2025-11-28 10:16:35 +01:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
tracing (source) dependencies patch 0.1.41 -> 0.1.43
tracing (source) workspace.dependencies patch 0.1.41 -> 0.1.43
tracing-subscriber (source) workspace.dependencies patch 0.3.20 -> 0.3.22

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

tokio-rs/tracing (tracing)

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: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

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.43` | | [tracing](https://tokio.rs) ([source](https://github.com/tokio-rs/tracing)) | workspace.dependencies | patch | `0.1.41` -> `0.1.43` | | [tracing-subscriber](https://tokio.rs) ([source](https://github.com/tokio-rs/tracing)) | workspace.dependencies | patch | `0.3.20` -> `0.3.22` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>tokio-rs/tracing (tracing)</summary> ### [`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**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, 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 [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS40My43IiwidXBkYXRlZEluVmVyIjoiNDEuNDMuNyIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
fix(deps): update rust crate tracing to v0.1.43
Some checks failed
/ clippy (pull_request) Failing after 2m27s
Details
068d3c91b6
renovate-bot bot force-pushed renovate/tokio-tracing-monorepo from 068d3c91b6
Some checks failed
/ clippy (pull_request) Failing after 2m27s
Details
to 9afe77d09b
Some checks failed
/ clippy (pull_request) Failing after 2m17s
Details
2025-11-28 11:04:26 +01:00 Compare
renovate-bot bot changed title from fix(deps): update rust crate tracing to v0.1.43 to fix(deps): update tokio-tracing monorepo 2025-11-28 11:04:27 +01:00
Some checks failed
/ clippy (pull_request) Failing after 2m17s
Required
Details
Some required checks were not successful.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/tokio-tracing-monorepo:renovate/tokio-tracing-monorepo
git switch renovate/tokio-tracing-monorepo
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
ci

   
crate/dtmm

   
crate/dtmt

   
crate/sdk

   
crate/serde_sjson
  
kind
bug
Something is not working

  
kind
documentation
Documentation needs to be adjusted

  
kind
enhancement
Improvement of existing functionality

  
kind
feature
New behaviour or functionality

  
kind
question
User is asking a question

  
kind
upstream
Root cause can be found in a dependency

  
part/bundle

   
part/filetype
  
stage
actionable

  
stage
design

  
stage
proposal

  
status/duplicate

This issue or pull request already exists

  
status/good first issue

Simple and/or isolated changes that can serve as an introduction to the code base

  
status/help wanted

   
status/invalid

Something is wrong

  
status
need-replicate
Additional information required to replicate the issue for debuggin

  
status/wontfix

This won't be fixed

No labels
ci
crate/dtmm
crate/dtmt
crate/sdk
crate/serde_sjson
kind
bug
kind
documentation
kind
enhancement
kind
feature
kind
question
kind
upstream
part/bundle
part/filetype
stage
actionable
stage
design
stage
proposal
status/duplicate
status/good first issue
status/help wanted
status/invalid
status
need-replicate
status/wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
bitsquid_dt/dtmt!319
No description provided.