Bump Microsoft.Diagnostics.Tracing.TraceEvent from 3.1.23 to 3.2.6 - #6034
Merged
Merged
Conversation
bart-vmware
force-pushed
the
patch-1
branch
from
September 16, 2026 07:59
8386a92 to
151b32b
Compare
bart-vmware
marked this pull request as ready for review
September 16, 2026 07:59
Contributor
Author
|
@hoyosjs Can you please review this PR? |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The dependency update has no unresolved review issues.
Pull request overview
Updates the centrally pinned TraceEvent dependency from 3.1.23 to 3.2.6 for diagnostics tooling and EventPipe libraries.
Changes:
- Bumps
MicrosoftDiagnosticsTracingTraceEventVersionto3.2.6.
File summaries
| File | Summary |
|---|---|
eng/Versions.props |
Updates the shared TraceEvent package version. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
max-charlamb
approved these changes
Sep 16, 2026
eng/Versions.props has pinned MicrosoftDiagnosticsTracingTraceEventVersion to 3.1.23 (released July 2025) for over a year, even though 3.2.6 (released August 2026) has been available for some time. This property is not tracked by Maestro dependency flow (see Version.Details.props), so it only ever moves when bumped by hand. This one property drives the TraceEvent/FastSerialization reference for dotnet-gcdump, dotnet-stack, dotnet-trace, dotnet-counters, dotnet-dsrouter, and Microsoft.Diagnostics.Monitoring.EventPipe, so all of them are currently built and tested against a Microsoft.Diagnostics. FastSerialization build that predates over a year of upstream fixes.
bart-vmware
force-pushed
the
patch-1
branch
from
September 17, 2026 07:40
151b32b to
70ca867
Compare
This was referenced Sep 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
eng/Versions.props has pinned MicrosoftDiagnosticsTracingTraceEventVersion to 3.1.23 (released July 2025) for over a year, even though 3.2.6 (released August 2026) has been available for some time. This property is not tracked by Maestro dependency flow (see Version.Details.props), so it only ever moves when bumped by hand.
This one property drives the TraceEvent/FastSerialization reference for dotnet-gcdump, dotnet-stack, dotnet-trace, dotnet-counters, dotnet-dsrouter, and Microsoft.Diagnostics.Monitoring.EventPipe, so all of them are currently built and tested against a Microsoft.Diagnostics.FastSerialization build that predates over a year of upstream fixes.