Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Apr 16, 2024

This PR contains the following updates:

Package Type Update Change
tracing (source) dependencies patch 0.1.26 -> 0.1.44
tracing-subscriber (source) dependencies minor 0.2 -> 0.3

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)

v0.1.41: tracing 0.1.41

Compare Source

[ crates.io ] | [ docs.rs ]

This release updates the tracing-core dependency to v0.1.33 and
the tracing-attributes dependency to v0.1.28.

Added
  • core: Add index API for Field (#​2820)
  • core: Allow &[u8] to be recorded as event/span field (#​2954)
Changed
  • Bump MSRV to 1.63 (#​2793)
  • core: Use const thread_locals when possible (#​2838)
Fixed
  • Removed core imports in macros (#​2762)
  • attributes: Added missing RecordTypes for instrument (#​2781)
  • attributes: Change order of async and unsafe modifier (#​2864)
  • Fix missing field prefixes (#​2878)
  • attributes: Extract match scrutinee (#​2880)
  • Fix non-simple macro usage without message (#​2879)
  • Fix event macros with constant field names in the first position (#​2883)
  • Allow field path segments to be keywords (#​2925)
  • core: Fix missed register_callsite error (#​2938)
  • attributes: Support const values for target and name (#​2941)
  • Prefix macro calls with ::core to avoid clashing with local macros (#​3024)

v0.1.40: tracing 0.1.40

Compare Source

This release fixes a potential stack use-after-free in the
Instrument::into_inner method. Only uses of this method are affected by this
bug.

Fixed
  • Use mem::ManuallyDrop instead of mem::forget in Instrument::into_inner
    (#​2765)

Thanks to @​cramertj and @​manishearth for finding and fixing this issue!

v0.1.39: tracing 0.1.39

Compare Source

This release adds several additional features to the tracing macros. In
addition, it updates the tracing-core dependency to v0.1.32 and
the tracing-attributes dependency to v0.1.27.

Added
  • Allow constant field names in macros (#​2617)
  • Allow setting event names in macros (#​2699)
  • core: Allow ValueSets of any length (#​2508)
Changed
  • tracing-attributes: updated to 0.1.27
  • tracing-core: updated to 0.1.32
  • attributes: Bump minimum version of proc-macro2 to 1.0.60 (#​2732)
  • attributes: Generate less dead code for async block return type hint (#​2709)
Fixed
  • Use fully qualified names in macros for items exported from std prelude
    (#​2621, #​2757)
  • attributes: Allow [clippy::let_with_type_underscore] in macro-generated
    code ([#​2609])
  • attributes: Allow unknown_lints in macro-generated code (#​2626)
  • attributes: Fix a compilation error in #[instrument] when the "log"
    feature is enabled (#​2599)
Documented
  • Add axum-insights to relevant crates. (#​2713)
  • Fix link to RAI pattern crate documentation ([#​2612])
  • Fix docs typos and warnings (#​2581)
  • Add clippy-tracing to related crates (#​2628)
  • Add tracing-cloudwatch to related crates (#​2667)
  • Fix deadlink to tracing-etw repo (#​2602)

v0.1.38: tracing 0.1.38

Compare Source

This tracing release changes the Drop implementation for Instrumented
Futures so that the attached Span is entered when dropping the Future. This
means that events emitted by the Future's Drop implementation will now be
recorded within its Span. It also adds #[inline] hints to methods called in
the event! macro's expansion, for an improvement in both binary size and
performance.

Additionally, this release updates the tracing-attributes dependency to
v0.1.24, which updates the syn dependency to v2.x.x.
tracing-attributes v0.1.24 also includes improvements to the #[instrument]
macro; see the tracing-attributes 0.1.24 release notes for
details.

Added
  • Instrumented futures will now enter the attached Span in their Drop
    implementation, allowing events emitted when dropping the future to occur
    within the span (#​2562)
  • #[inline] attributes for methods called by the event! macros, making
    generated code smaller (#​2555)
  • attributes: level argument to #[instrument(err)] and
    #[instrument(ret)] to override the level of
    the generated return value event (#​2335)
  • attributes: Improved compiler error message when #[instrument] is added to a const fn
    (#​2418)
Changed
  • tracing-attributes: updated to 0.1.24
  • Removed unneeded cfg-if dependency (#​2553)
  • attributes: Updated syn dependency to 2.0 (#​2516)
Fixed
  • attributes: Fix clippy::unreachable warnings in #[instrument]-generated code (#​2356)
  • attributes: Removed unused "visit" feature flag from syn dependency (#​2530)
Documented
  • attributes: Documented default level for #[instrument(err)] (#​2433)
  • attributes: Improved documentation for levels in #[instrument] (#​2350)

Thanks to @​nitnelave, @​jsgf, @​Abhicodes-crypto, @​LukeMathWalker, @​andrewpollack,
@​quad, @​klensy, @​davidpdrsn, @​dbidwell94, @​ldm0, @​NobodyXu, @​ilsv, and @​daxpedda
for contributing to this release!

v0.1.37: tracing 0.1.37

Compare Source

This release of tracing incorporates changes from tracing-core
v0.1.30 and tracing-attributes v0.1.23,
including the new Subscriber::on_register_dispatch method for performing late
initialization after a Subscriber is registered as a Dispatch, and bugfixes
for the #[instrument] attribute. Additionally, it fixes instances of the
bare_trait_objects lint, which is now a warning on tracing's MSRV and will
become an error in the next edition.

Fixed
  • attributes: Incorrect handling of inner attributes in #[instrument]ed
    functions (#​2307)
  • attributes: Incorrect location of compiler diagnostic spans generated for
    type errors in #[instrument]ed async fns (#​2270)
  • attributes: Updated syn dependency to fix compilation with -Z minimal-versions (#​2246)
  • bare_trait_objects warning in valueset! macro expansion (#​2308)
Added
  • core: Subscriber::on_register_dispatch method (#​2269)
  • core: WeakDispatch type and Dispatch::downgrade() function (#​2293)
Changed
  • tracing-core: updated to 0.1.30
  • tracing-attributes: updated to 0.1.23
Documented

Thanks to new contributors @​compiler-errors, @​e-nomem, @​WorldSEnder, @​Xiami2012,
and @​tl-rodrigo-gryzinski, as well as @​jswrenn and @​CAD97, for contributing to
this release!

v0.1.36: tracing 0.1.36

Compare Source

This release adds support for owned values and fat pointers as arguments to the
Span::record method, as well as updating the minimum tracing-core version
and several documentation improvements.

Fixed
  • Incorrect docs in dispatcher::set_default (#​2220)
  • Compilation with -Z minimal-versions (#​2246)
Added
Changed
  • tracing-core: updated to 0.1.29

Thanks to @​fredr, @​cgbur, @​jyn514, @​matklad, and @​CAD97 for contributing to this
release!

v0.1.35: tracing 0.1.35

Compare Source

This release reduces the overhead of callsite registration by using new
tracing-core APIs.

Added
  • Use DefaultCallsite to reduce callsite registration overhead (#​2083)
Changed
  • tracing-core: updated to 0.1.27

v0.1.34: tracing 0.1.34

Compare Source

This release includes bug fixes for the "log" support feature and for the use of
both scoped and global default dispatchers in the same program.

Fixed
  • Failure to use the global default dispatcher when a thread sets a local
    default dispatcher before the global default is set (#​2065)
  • log: Compilation errors due to async block/fn futures becoming !Send
    when the "log" feature flag is enabled (#​2073)
  • Broken links in documentation (#​2068)

Thanks to @​ben0x539 for contributing to this release!

v0.1.33: tracing 0.1.33

Compare Source

This release adds new span_enabled! and event_enabled! variants of the
enabled! macro, for testing whether a subscriber would specifically enable a
span or an event.

Added
Fixed
  • Compilation warning when compiling for <=32-bit targets (including wasm32)
    (#​2060)

Thanks to @​guswynn, @​arifd, @​hrxi, @​CAD97, and @​name1e5s for contributing to
this release!

v0.1.32: tracing 0.1.32

Compare Source

This release reduces the overhead of creating and dropping disabled
spans significantly, which should improve performance when no tracing
subscriber is in use or when spans are disabled by a filter.

Fixed
  • attributes: Compilation failure with --minimal-versions due to a
    too-permissive syn dependency (#​1960)
Changed
  • Reduced Drop overhead for disabled spans (#​1974)
  • tracing-attributes: updated to 0.1.20

v0.1.31: tracing 0.1.31

Compare Source

This release increases the minimum supported Rust version (MSRV) to 1.49.0. In
addition, it fixes some relatively rare macro bugs.

Added
  • Added tracing-forest to the list of related crates (#​1935)
Changed
  • Updated minimum supported Rust version (MSRV) to 1.49.0 (#​1913)
Fixed
  • Fixed the warn! macro incorrectly generating an event with the TRACE level
    (#​1930)
  • Fixed macro hygiene issues when used in a crate that defines its own concat!
    macro, for real this time (#​1918)

Thanks to @​QnnOkabayashi, @​nicolaasg, and @​teohhanhui for contributing to this
release!

v0.1.30: tracing 0.1.30

Compare Source

This release adds experimental support for recording structured field
values using the valuable crate. See this blog post for
details on valuable.

Note that valuable support currently requires --cfg tracing_unstable. See
the documentation for details.

This release also adds a new enabled! macro for testing if a span or event
would be enabled.

Added
Changed
  • tracing-core: updated to 0.1.22
  • tracing-attributes: updated to 0.1.19
Fixed
  • log: Fixed "use of moved value" compiler error when the "log" feature is
    enabled (#​1823)
  • Fixed macro hygiene issues when used in a crate that defines its own concat!
    macro (#​1842)
  • A very large number of documentation fixes and improvements.

Thanks to @​@​Vlad-Scherbina, @​Skepfyr, @​Swatinem, @​guswynn, @​teohhanhui,
@​xd009642, @​tobz, @​d-e-s-o@​0b01, and @​nickelc for contributing to this release!

v0.1.29: tracing 0.1.29

Compare Source

This release adds support for recording Option<T> where T: Value as
typed tracing field values. It also includes significant performance
improvements for functions annotated with the #[instrument] attribute
when the generated span is disabled.

Changed
  • tracing-core: updated to v0.1.21
  • tracing-attributes: updated to v0.1.19
Added
Fixed
  • instrument: added missing Future implementation for
    WithSubscriber, making the WithDispatch extension trait actually
    useable (#​1602)
  • Documentation fixes and improvements (#​1595, #​1601, #​1597)

Thanks to @​BrianBurgers, @​mattiast, @​DCjanus, @​oli-obk, and @​matklad for
contributing to this release!

v0.1.28: tracing 0.1.28

Compare Source

0.1.28 (September 17th, 2021)

This release fixes an issue where the RustDoc documentation was rendered
incorrectly. It doesn't include any actual code changes, and is very
boring and can be ignored.

Fixed
  • docs: Incorrect documentation rendering due to unclosed <div>
    tag (#​1572)

v0.1.27: tracing 0.1.27

Compare Source

This release adds a new Span::or_current method to aid in
efficiently propagating span contexts to spawned threads or tasks.
Additionally, it updates the tracing-core version to 0.1.20 and
the tracing-attributes version to 0.1.16, ensuring that a number
of new features in those crates are present.

Fixed
  • instrument: Added missing WithSubscriber implementations for
    futures and other types (#​1424)
Added
  • Span::or_current method, to help with efficient span context
    propagation (#​1538)
  • attributes: add skip_all option to #[instrument] (#​1548)
  • attributes: record primitive types as primitive values rather than
    as fmt::Debug (#​1378)
  • core: NoSubscriber, a no-op Subscriber implementation
    (#​1549)
  • core: Added Visit::record_f64 and support for recording
    floating-point values (#​1507, #​1522)
  • A large number of documentation improvements and fixes (#​1369,
    #​1398, #​1435, #​1442, #​1524, #​1556)

Thanks to new contributors @​dzvon and @​mbergkvist, as well as @​teozkr,
@​maxburke, @​LukeMathWalker, and @​jsgf, for contributing to this release!


Configuration

📅 Schedule: 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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Author

renovate bot commented Apr 16, 2024

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path experimental/udev-device-manager/Cargo.toml --workspace
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/experimental/udev-device-manager/Cargo.toml
workspace: /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/Cargo.toml

this may be fixable by adding `experimental/udev-device-manager` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/udev-device-manager/Cargo.toml --package [email protected] --precise 0.3.18
    Updating crates.io index
error: failed to select a version for the requirement `tracing-subscriber = "^0.2.2"`
candidate versions found which didn't match: 0.3.18
location searched: crates.io index
required by package `tracing-error v0.1.2`
    ... which satisfies dependency `tracing-error = "^0.1.2"` (locked to 0.1.2) of package `color-eyre v0.5.11`
    ... which satisfies dependency `color-eyre = "^0.5"` (locked to 0.5.11) of package `k8s-udev-device-manager v0.0.0 (/tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/crates/udev-device-manager)`
perhaps a crate was updated and forgotten to be re-vendored?

@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch from c48e395 to ee28de0 Compare May 1, 2024 10:31
@renovate renovate bot changed the title Update Rust crate tracing-subscriber to 0.3 Update tokio-tracing monorepo May 1, 2024
@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch from ee28de0 to 2580d82 Compare May 5, 2024 13:22
@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch from 2580d82 to a287a7c Compare November 27, 2024 19:29
@renovate
Copy link
Author

renovate bot commented Nov 27, 2024

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/udev-device-manager/Cargo.toml --package [email protected] --precise 0.3.22
    Updating crates.io index
error: failed to select a version for the requirement `tracing-subscriber = "^0.2.2"`
candidate versions found which didn't match: 0.3.22
location searched: crates.io index
required by package `tracing-error v0.1.2`
    ... which satisfies dependency `tracing-error = "^0.1.2"` (locked to 0.1.2) of package `color-eyre v0.5.11`
    ... which satisfies dependency `color-eyre = "^0.5"` (locked to 0.5.11) of package `k8s-udev-device-manager v0.0.0 (/tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/crates/udev-device-manager)`

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path experimental/udev-device-manager/Cargo.toml --package [email protected] --precise 0.1.44
error: current package believes it's in a workspace when it's not:
current:   /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/experimental/udev-device-manager/Cargo.toml
workspace: /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/Cargo.toml

this may be fixable by adding `experimental/udev-device-manager` to the `workspace.members` array of the manifest located at: /tmp/renovate/repos/github/YoloDev/kubelet-deviceplugin-rs/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.

@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch from a287a7c to 618413d Compare August 10, 2025 13:59
@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch from 618413d to e0598f3 Compare August 31, 2025 11:28
@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch from e0598f3 to efd0a75 Compare September 25, 2025 14:13
@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch 3 times, most recently from f6fa0be to f13f92b Compare November 28, 2025 14:37
@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch from f13f92b to 303b3fd Compare December 10, 2025 13:11
@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch from 303b3fd to f3ea8d5 Compare December 18, 2025 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant