fix(deps): update tokio-tracing monorepo

[xentra-bot]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
tracing (source)	dependencies	patch	0.1.37 -> 0.1.40
tracing-subscriber (source)	dependencies	patch	0.3.17 -> 0.3.18

---

Release Notes

tokio-rs/tracing (tracing)

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

---

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 has been generated by Renovate Bot.