[dependabot]

Updated ModelContextProtocol.AspNetCore from 2.2.0 to 2.3.0.

Release notes

Sourced from ModelContextProtocol.AspNetCore's releases.

2.3.0

This release improves HTTP discovery, OAuth, protocol interoperability, and shutdown reliability, preserves registration order for server primitives, and exposes a TimeProvider for deterministic client timeout tests. It also corrects optional server-identity handling; applications reading McpClient.ServerInfo should adopt nullable handling.

Breaking Changes

Refer to the C# SDK Versioning documentation for details on versioning and breaking change policies.

1. McpClient.ServerInfo is nullable — #​1903
   • Its return annotation changes from Implementation to Implementation?. Existing non-nullable assignments or dereferences can produce nullable warnings and fail warnings-as-errors builds.
   • On 2026-07-28 connections, ServerInfo is null when the server omits optional identity metadata from server/discover. Legacy initialize still requires serverInfo. Reading the property before connecting still throws InvalidOperationException.
   • Migrate with a null check or a fallback such as client.ServerInfo?.Name ?? "Unknown server". Self-reported identity must not be used for security decisions.
   • This corrective source-compatibility change is intentionally included in 2.3.0.

What's Changed

• Correct protocol-version telemetry for stateless server spans #​1810 by @​luisangelrod
• Preserve HTTP errors and correct discovery fallback handling #​1791 by @​PranavSenthilnathan (co-authored by @​Copilot)
• Make modern Streamable HTTP status mapping deterministic #​1837 by @​jstar0
  • Modern responses wait for the first protocol message before sending headers; long-running silent handlers may need progress output or an appropriate HTTP timeout. Legacy eager-header behavior is preserved.
• Accept opaque legacy metadata and correct request-scoped capabilities and discovery advertisement #​1852 by @​halter73 (co-authored by @​Copilot)
• Avoid redundant SSE fallback after discovery is rejected with 400 or 404 #​1855 by @​scottt732
• Close server stdin before waiting for graceful stdio process exit #​1838 by @​luisangelrod
• Preserve insertion order when listing server tools, prompts, and resources #​1924 by @​PederHP (co-authored by Claude Opus 5.5)
• Allow missing optional server identity in discovery and make ServerInfo nullable #​1903 by @​Coding-Professional
• Include JSON parse details in Streamable HTTP 400 responses #​1844 by @​ump45nose
• Exclude OAuth from DiscoverProbeTimeout, expose McpClientOptions.TimeProvider for deterministic timeout tests, and default SSE to legacy initialization #​1719 by @​halter73 (co-authored by @​Copilot)
  • OAuth remains subject to the overall InitializationTimeout and caller cancellation; it is excluded only from the short discovery-probe budget.
  • Modern discovery over SSE requires both explicit HttpTransportMode.Sse and ProtocolVersion = "2026-07-28"; pinning the version with AutoDetect is not equivalent.
• Preserve numeric progress tokens in RequestOptions serialization #​1832 by @​dfedoryshchev
• Dispose legacy SSE POST responses to release connections deterministically #​1841 by @​yalcinfu22 (co-authored by Claude Fable 5)

Documentation Updates

• Document standing support for new MCP specification revisions #​1826 by @​halter73 (co-authored by @​Copilot)

Test Improvements

• Stabilize discovery-capable test connections while retaining initialization deadlines #​1943 by @​tarekgh

Repository Infrastructure Updates

• Add a source selector for manual documentation publishes #​1828 by @​jeffhandley (co-authored by @​Copilot)
• Update SourceLink's private build dependency to resolve a vulnerable Git dependency #​1873 by @​halter73 (co-authored by @​Copilot)
• Correct obsolete McpServerFactory references in Copilot instructions #​1892 by @​Zir0-93
• Update Microsoft.Extensions.AI and AI.Abstractions to 10.11.0 and align shared System dependencies to 10.0.13 #​1940

Acknowledgements

• @​scottt732 made their first contribution in #​1855
• @​Zir0-93 made their first contribution in #​1892
• @​Coding-Professional made their first contribution in #​1903
  ... (truncated)

Commits viewable in compare view.

Updated OpenTelemetry.Api from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Api'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.EmitLog ignoring
    instrumentation 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 NaN value 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 for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or 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.EmitLog ignoring
    instrumentation 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 NaN value 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 for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or SelfDiagnosticsOptions, are now always created as new files.
    (#​7968)

  • Self-diagnostics messages written to the sinks configured by
    SelfDiagnosticsOptions are 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_info and configured
    resource 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_info and configured
    resource 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

  • Updated OpenTelemetry core component version(s) to 1.20.1.
    (#​7990)

  See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Exporter.Console from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Exporter.Console'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.EmitLog ignoring
    instrumentation 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 NaN value 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 for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or 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.EmitLog ignoring
    instrumentation 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 NaN value 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 for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or SelfDiagnosticsOptions, are now always created as new files.
    (#​7968)

  • Self-diagnostics messages written to the sinks configured by
    SelfDiagnosticsOptions are 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_info and configured
    resource 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_info and configured
    resource 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

  • Updated OpenTelemetry core component version(s) to 1.20.1.
    (#​7990)

  See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol'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.EmitLog ignoring
    instrumentation 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 NaN value 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 for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or 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.EmitLog ignoring
    instrumentation 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 NaN value 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 for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or SelfDiagnosticsOptions, are now always created as new files.
    (#​7968)

  • Self-diagnostics messages written to the sinks configured by
    SelfDiagnosticsOptions are 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_info and configured
    resource 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_info and configured
    resource 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

  • Updated OpenTelemetry core component version(s) to 1.20.1.
    (#​7990)

  See CHANGELOG for details.

Commits viewable in compare view.

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.EmitLog ignoring
    instrumentation 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 NaN value 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 for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or 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.EmitLog ignoring
    instrumentation 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 NaN value 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 for
    export when an exporter stops enumerating a single-item or array
    Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
    on the same provider to export missing or incorrect data.
    (#​7965)

  • Fixed a SuppressInstrumentationScope.Enter() reference count never being
    released when the Activity it was entered for is not recorded, which caused
    all subsequent telemetry in that execution context to be suppressed.
    (#​7966)

  • Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
    or SelfDiagnosticsOptions, are now always created as new files.
    (#​7968)

  • Self-diagnostics messages written to the sinks configured by
    SelfDiagnosticsOptions are 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_info and configured
    resource 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_info and configured
    resource 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

  • Updated OpenTelemetry core component version(s) to 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions