Skip to content

chore(deps): bump the OpenTelemetry packages together to 1.19 - #238

Open
ShortArrow wants to merge 1 commit into
mainfrom
chore/deps-opentelemetry-1.19
Open

ShortArrow wants to merge 1 commit into
mainfrom
chore/deps-opentelemetry-1.19

Conversation

@ShortArrow

@ShortArrow ShortArrow commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Why not #236

#236 moved only OpenTelemetry.Exporter.OpenTelemetryProtocol to 1.19.1. The exporter requires the OpenTelemetry SDK 1.19.1, so the CLI's lock file resolved the SDK at 1.19.1. OpenTelemetry.Extensions.Hosting and OpenTelemetry.Instrumentation.AspNetCore stayed at 1.18.0, and IviCli.Cli.Tests resolved the SDK at 1.18.0. The tests would then have run against a different OpenTelemetry than the one that ships.

What changes

All three pinned packages move together: Hosting and the exporter to 1.19.1, and Instrumentation.AspNetCore to 1.19.0, its latest release. After the bump, every OpenTelemetry package resolves to a single version in every lock file.

.github/dependabot.yml gets an opentelemetry group for OpenTelemetry*, the same way the Microsoft.Extensions and TestableIO packages are already grouped. The family then arrives in one PR.

Verification

Locked restore, the build, the analyzers and the whole test suite pass on Windows. The third-party notices list is unchanged, because the set of shipped package names is the same.

Supersedes #236, which moved only the OTLP exporter to 1.19.1; that
pulled the OpenTelemetry SDK to 1.19.1 in the CLI while Extensions.Hosting
and Instrumentation.AspNetCore stayed at 1.18.0, and the CLI's tests
resolved the SDK at 1.18.0. A Dependabot group now keeps the family in
one PR.
@ShortArrow
ShortArrow marked this pull request as ready for review September 28, 2026 08:01
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.

1 participant