Repository navigation
Bump OpenTelemetry.Extensions.Hosting from 1.20.0 to 1.20.1 - #3381
Merged
Conversation
--- updated-dependencies: - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3381 +/- ##
=======================================
Coverage 30.95% 30.95%
=======================================
Files 41 41
Lines 743 743
Branches 21 21
=======================================
Hits 230 230
Misses 509 509
Partials 4 4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
dependabot
Bot
deleted the
dependabot/nuget/BervProject.WebApi.Boilerplate.ServiceDefaults/OpenTelemetry.Extensions.Hosting-1.20.1
branch
October 21, 2026 01:15
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.
Updated OpenTelemetry.Extensions.Hosting from 1.20.0 to 1.20.1.
Release notes
Sourced from OpenTelemetry.Extensions.Hosting's releases.
1.20.1
For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.
The following changes are from the previous release 1.20.0.
NuGet: OpenTelemetry v1.20.1
Fixed a possible race condition on ARM64 when multiple threads record the
first measurement with no tags, or the first overflow measurement, that could
cause the measurement to be recorded incorrectly.
(#7951)
Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
and prefixed JWTs.
(#7955)
Fixed default HTTP client log filtering when registering the OTLP log exporter
through
OpenTelemetryLoggerOptions.(#7959)
Fixed legacy self-diagnostics logging terminating the process when the log
file is truncated or the log volume runs out of space.
(#7956)
Experimental (pre-release builds only): Fixed
Logger.EmitLogignoringinstrumentation suppression, which could cause recursive exports or deadlocks.
(#7961)
Fixed delta double counters losing subsequent measurements after a non-finite
or large value and idle metric points with a
NaNvalue failing to be reclaimed.(#7963)
Improve the assignment of values to exponential histogram buckets when the
value is near a bucket boundary by using a pre-computed lookup table.
(#7911)
Fixed
LogRecords being returned to the shared pool while still queued forexport when an exporter stops enumerating a single-item or array
Batch<LogRecord>early which could cause aBatchLogRecordExportProcessoron the same provider to export missing or incorrect data.
(#7965)
Fixed a
SuppressInstrumentationScope.Enter()reference count never beingreleased when the
Activityit was entered for is not recorded, which causedall subsequent telemetry in that execution context to be suppressed.
(#7966)
Self-diagnostics log files, whether configured through
OTEL_DIAGNOSTICS.jsonor
SelfDiagnosticsOptions, are now always created as new files.(#7968)
... (truncated)
1.20.1-rc.1
The following changes are from the previous release 1.20.0.
NuGet: OpenTelemetry v1.20.1-rc.1
Fixed a possible race condition on ARM64 when multiple threads record the
first measurement with no tags, or the first overflow measurement, that could
cause the measurement to be recorded incorrectly.
(#7951)
Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
and prefixed JWTs.
(#7955)
Fixed default HTTP client log filtering when registering the OTLP log exporter
through
OpenTelemetryLoggerOptions.(#7959)
Fixed legacy self-diagnostics logging terminating the process when the log
file is truncated or the log volume runs out of space.
(#7956)
Experimental (pre-release builds only): Fixed
Logger.EmitLogignoringinstrumentation suppression, which could cause recursive exports or deadlocks.
(#7961)
Fixed delta double counters losing subsequent measurements after a non-finite
or large value and idle metric points with a
NaNvalue failing to be reclaimed.(#7963)
Improve the assignment of values to exponential histogram buckets when the
value is near a bucket boundary by using a pre-computed lookup table.
(#7911)
Fixed
LogRecords being returned to the shared pool while still queued forexport when an exporter stops enumerating a single-item or array
Batch<LogRecord>early which could cause aBatchLogRecordExportProcessoron the same provider to export missing or incorrect data.
(#7965)
Fixed a
SuppressInstrumentationScope.Enter()reference count never beingreleased when the
Activityit was entered for is not recorded, which causedall subsequent telemetry in that execution context to be suppressed.
(#7966)
Self-diagnostics log files, whether configured through
OTEL_DIAGNOSTICS.jsonor
SelfDiagnosticsOptions, are now always created as new files.(#7968)
Self-diagnostics messages written to the sinks configured by
SelfDiagnosticsOptionsare now truncated to 16,384 characters so that the... (truncated)
1.20.1-beta.1
The following changes are from the previous release 1.20.0-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1
Fixed scrape responses being handed to the server in a single write, which
made the server buffer a full copy of the response for each client that did
not read it until the request completed or timed out. Responses are now
written in bounded slices so the server's back-pressure applies.
(#7957)
Fixed startup scrapes permanently omitting
target_infoand configuredresource constant labels from subsequent scrape responses.
(#7984)
Updated OpenTelemetry core component version(s) to
1.20.1.(#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1
Fixed scrape responses being handed to the server in a single write, which
on Linux and macOS made the listener allocate and hold a full copy of the
response for each client that did not read it until the request completed or
timed out. Responses are now written in bounded slices.
(#7957)
Fixed scrape requests that announce a request body holding a thread pool
thread after their response had been sent on Linux and macOS for as long as
the client kept trickling in the body. The connection is now closed after
responding to a request with a body instead of being kept alive.
(#7962)
Fixed startup scrapes permanently omitting
target_infoand configuredresource constant labels from subsequent scrape responses.
(#7984)
Updated OpenTelemetry core component version(s) to
1.20.1.(#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1
1.20.1.(#7990)
See CHANGELOG for details.
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)