chore(deps): update OpenTelemetry to 1.18.0 and Spectre.Console to 0.57.2 - #190
Merged
Conversation
…57.2 Dependabot cannot land NuGet bumps here: a lock file holding a package as CentralTransitive fails locked restore with NU1004, so the version and the lock files move together in one hand-made change.
This was referenced Aug 25, 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
1 participant
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.
Supersedes #182 and #183, which cannot merge on their own.
Why by hand
Dependabot's NuGet PRs fail restore in 23–31 seconds with
NU1004: a package held asCentralTransitivein a lock file no longer matches central package management once the version moves, and locked restore refuses. Dependabot editsDirectory.Packages.propswithout regenerating the 28 lock files, so its NuGet PRs are structurally unable to go green here. The fix is a single change that moves the version and the lock files together, viadotnet restore --force-evaluate.Contents
All three OpenTelemetry packages go to 1.18.0 rather than the two Dependabot proposed —
Exporter.OpenTelemetryProtocolwas left at 1.17.0 by its split, and a mixed OTel stack is not worth the risk of finding out about. Spectre.Console 0.57.1 → 0.57.2 while here.dotnet list package --outdatedis empty afterwards.Not a security update
Worth stating plainly, since this is dependency work: there is nothing to patch. Zero open Dependabot alerts, and
dotnet list package --vulnerable --include-transitivereports no vulnerable packages across all twelve projects. This is freshness, not remediation.Full suite green (12 assemblies). The telemetry tests exercise the ActivitySource and Meter paths these packages sit behind.