Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 26, 2025

This PR contains the following updates:

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

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: 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 renovate bot changed the title Update tokio-tracing monorepo Update Rust crate tracing-subscriber to v0.3.21 Nov 26, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Nov 26, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact 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 Cargo.toml --package tracing-subscriber@0.3.20 --precise 0.3.21
    Updating crates.io index
error: failed to select a version for the requirement `tracing = "^0.1.42"`
  version 0.1.42 is yanked
location searched: crates.io index
required by package `tracing-subscriber v0.3.21`
    ... which satisfies dependency `tracing-subscriber = "^0.3.18"` of package `h2test v0.1.0 (/tmp/renovate/repos/github/EEWBot/h2test)`

@renovate renovate bot changed the title Update Rust crate tracing-subscriber to v0.3.21 Update Rust crate tracing-subscriber to v0.3.21 - autoclosed Nov 26, 2025
@renovate renovate bot closed this Nov 26, 2025
@renovate renovate bot deleted the renovate/tokio-tracing-monorepo branch November 26, 2025 21:28
@renovate renovate bot changed the title Update Rust crate tracing-subscriber to v0.3.21 - autoclosed Update tokio-tracing monorepo Nov 28, 2025
@renovate renovate bot reopened this Nov 28, 2025
@renovate renovate bot force-pushed the renovate/tokio-tracing-monorepo branch 2 times, most recently from bbcfc54 to aa05f72 Compare November 28, 2025 10:42
@yanorei32 yanorei32 merged commit 6523702 into master Nov 29, 2025
3 checks passed
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.

2 participants