[release/8.0] Update to 1.8.1 of OpenTelemetry dependencies #3843
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.
Backport of #3842 to release/8.0
/cc @eerhardt
Customer Impact
When customers make a new Aspire template, they automatically get notified that there are updates to these OTel packages.
This version fixes a native AOT regression that happened in
1.8.0
. See https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.8.1Testing
automated tests
Risk
Low. There were only 2 fixes in this new version.
Regression?
Yes.
OpenTelemetry.Exporter.OpenTelemetryProtocol
before1.8.0
was native AOT compatible. With the latest Aspire template an app gets AOT warnings from insideOpenTelemetry.Exporter.OpenTelemetryProtocol
.Microsoft Reviewers: Open in CodeFlow