kjuulh/dagger-components
1
0
Fork 0
Code Issues 1 Pull Requests 4 Packages Projects Releases 3 Wiki Activity

fix(deps): update rust crate tracing to v0.1.43 #72

Open
kjuulh wants to merge 1 commits from renovate/tokio-tracing-monorepo into main
pull from: renovate/tokio-tracing-monorepo
merge into: kjuulh:main
Conversation 0 Commits 1 Files Changed 1 +6 -6
kjuulh commented 2025-11-29 02:25:23 +01:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
tracing (source) dependencies patch 0.1.41 -> 0.1.43

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][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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • 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` | --- ### 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`]\[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. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjM5LjI2NC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
kjuulh added 1 commit 2025-11-29 02:25:24 +01:00
fix(deps): update rust crate tracing to v0.1.43 42b0ec7b1e
kjuulh scheduled this pull request to auto merge when all checks succeed 2025-11-29 02:25:24 +01:00
Some required checks are missing.
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 checkout renovate/tokio-tracing-monorepo
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kjuulh
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kjuulh/dagger-components#72
No description provided.
Delete Branch "renovate/tokio-tracing-monorepo"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?