generated from lucas/rust-webserver-template
chore(deps): update tokio-tracing monorepo (master) #9
No reviewers
Labels
No labels
Agent
Ignore
Agent
In Progress
Agent
Planned
Agent
Planning
Agent
Ready
Agent
Triage
Compat/Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Tag/Good First Issue
Tag/Help Wanted
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
lucas/logview!9
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/master-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?
This PR contains the following updates:
0.1.41→0.1.440.3.19→0.3.23Release Notes
tokio-rs/tracing (tracing)
v0.1.44: tracing 0.1.44Compare Source
Fixed
record_allpanic (#3432)Changed
tracing-core: updated to 0.1.36 (#3440)v0.1.43: tracing 0.1.43Compare 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
valuesetmacro sanitary" (#3425)v0.1.42: tracing 0.1.42Compare Source
Important
The
Span::record_allmethod has been removed from the documented API. Itwas always unsuable via the documented API as it requried a
ValueSetwhichhas no publically documented constructors. The method remains, but should not
be used outside of
tracingmacros.Added
record_all!macro for recording multiple values in one call (#3227)Changed
tracing-core: updated to 0.1.35 (#3414)tracing-attributes: updated to 0.1.31 (#3417)Fixed
event!(#2983)release_max_level_*not set (#3373)valuesetmacro sanitary (#3382)Documented
dynkeyword inVisitdocumentation code sample (#3387)Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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.
This PR has been generated by Mend Renovate.
Lockfile-only patch bump; no source changes needed.
tracing0.1.41→0.1.44,tracing-core0.1.34→0.1.36,tracing-attributes0.1.30→0.1.31,tracing-subscriber0.3.19→0.3.23. All within the existing caret ranges inCargo.toml(tracing = "0.1.41",tracing-subscriber = "0.3.19"), so no manifest edit is required.tracing-error = "0.2.1"depends ontracing-subscriber ^0.3and resolves unchanged.valuesetchange) is not what's being pulled in — 0.1.44 contains the revert from 0.1.43 plus therecord_allpanic fix. Neitherrecord_allnorValueSetis used anywhere in this tree, so the API churn is a non-event here.tracing-subscriberswappedregexforregex-automata, which letsmatchers0.1→0.2 drop the ancientregex-automata 0.1/regex-syntax 0.6pair, andnu-ansi-term0.46→0.50.3 replaceswinapi/overloadwithwindows-sys 0.61.2(already in the graph). Net −2 duplicate regex trees and the lastwinapi0.3 usage gone.d9315d6is green on all three jobs (check, test, image).