[dependabot]

Updated Aspire.Hosting.JavaScript from 13.6.1 to 13.6.4.

Release notes

Sourced from Aspire.Hosting.JavaScript's releases.

13.6.4

What's New in Aspire 13.6.4

Patch release for Aspire 13.6 that improves resource startup reliability, fixes Azure publishing with parameterized enum properties in TypeScript AppHosts, and tightens CLI diagnostic log permissions on Unix.

🐛 Fixes

• 🖥️ Resources could fail to start after a DCP create request timed out — AppHost now checks whether a resource was created before retrying a timed-out or HTTP 504 request, avoiding a premature FailedToStart state when DCP completed the operation. API operations default to a 40-second timeout with an additional 20-second allowance before the first successful operation, and resource creation has a two-minute recovery budget. These limits can be configured through DcpPublisher:KubernetesApiTimeout, DcpPublisher:KubernetesInitializationAdditionalTimeout, and DcpPublisher:KubernetesCreateRecoveryTimeout. Established watch and log streams are not limited by these operation timeouts. Addresses startup timeouts reported in 13.6. Fixes #​20691. (#​20868, backport of #​20752, @​danegsta)

• ☁️ TypeScript AppHosts could fail to publish parameterized Azure enum properties — Assigning a bicep().parameter(...) expression to an enum-valued provisioning property, such as an Azure Storage SKU name, now works instead of failing with a type-assignment error. Type checking for literal values and incompatible expression types is preserved. Fixes a scenario introduced with the Azure provisioning proxy feature in 13.6. (#​20767, backport of #​20557, @​sebastienros)

• 🔒 CLI diagnostic logs now use owner-only permissions on Unix — Log files are restricted to owner read/write access (0600), including reused files, and the dedicated Aspire logs directory uses owner-only access (0700), repairing existing permissions when needed. Newly created custom log directories also use 0700; existing custom parent directories and Windows permission behavior are unchanged. Diagnostic logs can contain sensitive data, including dashboard login URLs, so review them before sharing. (#​21282, backport of #​21276, @​mitchdenny)

---

Full Changelog: v13.6.3...v13.6.4

Full commit: c89352703f78ae46de90fbf751ed8b52b77b89bf

13.6.3

What's New in Aspire 13.6.3

Patch release for Aspire 13.6 that improves resource orchestration reliability by preventing unread resource watches from stalling resource updates and operations.

🐛 Fixes

• 🖥️ Resource operations could stall when a watch stopped being read — AppHost now closes abandoned watch connections when setup is canceled and keeps reading resource events even when event handlers are slow. Resource event ordering, lifecycle callback dispatch, and the existing periodic reconnection safeguard are preserved. (#​21002, backport of #​20972, @​danegsta)

• 🔄 Slow watchers could block other resource updates or watcher shutdown — The bundled Developer Control Plane (DCP) is updated to 0.26.6, which keeps internal lifecycle watches draining and uses bounded, asynchronous watch delivery to prevent unread watches from blocking resource-change publication and unrelated watcher shutdown. (#​21215, @​danegsta; includes microsoft/dcp#​307)

---

Full Changelog: v13.6.2...v13.6.3

Full commit: 38294b1b31552dae42a516cffa0cbc737ec08976

13.6.2

Full commit: af07e33f8d1ef733645138b3f8e36067d073148d

What's Changed

• [release/13.6] Bump version to 13.6.2 by @​danegsta with @​Copilot in [release/13.6] Bump version to 13.6.2 microsoft/aspire#20877
• [release/13.6] Pin MessagePack to 2.5.307 for security fixes by @​eerhardt in [release/13.6] Pin MessagePack to 2.5.307 for security fixes microsoft/aspire#21156

Full Changelog: microsoft/aspire@v13.6.1...v13.6.2

Commits viewable in compare view.

Updated Aspire.Hosting.PostgreSQL from 13.6.1 to 13.6.4.

Release notes

Sourced from Aspire.Hosting.PostgreSQL's releases.

13.6.4

What's New in Aspire 13.6.4

Patch release for Aspire 13.6 that improves resource startup reliability, fixes Azure publishing with parameterized enum properties in TypeScript AppHosts, and tightens CLI diagnostic log permissions on Unix.

🐛 Fixes

• 🖥️ Resources could fail to start after a DCP create request timed out — AppHost now checks whether a resource was created before retrying a timed-out or HTTP 504 request, avoiding a premature FailedToStart state when DCP completed the operation. API operations default to a 40-second timeout with an additional 20-second allowance before the first successful operation, and resource creation has a two-minute recovery budget. These limits can be configured through DcpPublisher:KubernetesApiTimeout, DcpPublisher:KubernetesInitializationAdditionalTimeout, and DcpPublisher:KubernetesCreateRecoveryTimeout. Established watch and log streams are not limited by these operation timeouts. Addresses startup timeouts reported in 13.6. Fixes #​20691. (#​20868, backport of #​20752, @​danegsta)

• ☁️ TypeScript AppHosts could fail to publish parameterized Azure enum properties — Assigning a bicep().parameter(...) expression to an enum-valued provisioning property, such as an Azure Storage SKU name, now works instead of failing with a type-assignment error. Type checking for literal values and incompatible expression types is preserved. Fixes a scenario introduced with the Azure provisioning proxy feature in 13.6. (#​20767, backport of #​20557, @​sebastienros)

• 🔒 CLI diagnostic logs now use owner-only permissions on Unix — Log files are restricted to owner read/write access (0600), including reused files, and the dedicated Aspire logs directory uses owner-only access (0700), repairing existing permissions when needed. Newly created custom log directories also use 0700; existing custom parent directories and Windows permission behavior are unchanged. Diagnostic logs can contain sensitive data, including dashboard login URLs, so review them before sharing. (#​21282, backport of #​21276, @​mitchdenny)

---

Full Changelog: v13.6.3...v13.6.4

Full commit: c89352703f78ae46de90fbf751ed8b52b77b89bf

13.6.3

What's New in Aspire 13.6.3

Patch release for Aspire 13.6 that improves resource orchestration reliability by preventing unread resource watches from stalling resource updates and operations.

🐛 Fixes

• 🖥️ Resource operations could stall when a watch stopped being read — AppHost now closes abandoned watch connections when setup is canceled and keeps reading resource events even when event handlers are slow. Resource event ordering, lifecycle callback dispatch, and the existing periodic reconnection safeguard are preserved. (#​21002, backport of #​20972, @​danegsta)

• 🔄 Slow watchers could block other resource updates or watcher shutdown — The bundled Developer Control Plane (DCP) is updated to 0.26.6, which keeps internal lifecycle watches draining and uses bounded, asynchronous watch delivery to prevent unread watches from blocking resource-change publication and unrelated watcher shutdown. (#​21215, @​danegsta; includes microsoft/dcp#​307)

---

Full Changelog: v13.6.2...v13.6.3

Full commit: 38294b1b31552dae42a516cffa0cbc737ec08976

13.6.2

Full commit: af07e33f8d1ef733645138b3f8e36067d073148d

What's Changed

• [release/13.6] Bump version to 13.6.2 by @​danegsta with @​Copilot in [release/13.6] Bump version to 13.6.2 microsoft/aspire#20877
• [release/13.6] Pin MessagePack to 2.5.307 for security fixes by @​eerhardt in [release/13.6] Pin MessagePack to 2.5.307 for security fixes microsoft/aspire#21156

Full Changelog: microsoft/aspire@v13.6.1...v13.6.2

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.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.

Updated OpenTelemetry.Instrumentation.AspNetCore from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.

1.20.1

• NuGet: OpenTelemetry.Extensions.AWS v1.20.1

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

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Instrumentation.AWS v1.20.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.1

  No notable changes.

  See CHANGELOG for details.

1.20.1-rc.1

• NuGet: OpenTelemetry.Instrumentation.Process v1.20.1-rc.1

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

  See CHANGELOG for details.

1.20.1-beta.1

• NuGet: OpenTelemetry.Extensions.Enrichment v1.20.1-beta.1

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

  See CHANGELOG for details.

1.20.1-alpha.1

• NuGet: OpenTelemetry.Instrumentation.EventCounters v1.20.1-alpha.1

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

  See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.Http from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Instrumentation.Http's releases.

1.20.1

• NuGet: OpenTelemetry.Extensions.AWS v1.20.1

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

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Instrumentation.AWS v1.20.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.1

  No notable changes.

  See CHANGELOG for details.

1.20.1-rc.1

• NuGet: OpenTelemetry.Instrumentation.Process v1.20.1-rc.1

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

  See CHANGELOG for details.

1.20.1-beta.1

• NuGet: OpenTelemetry.Extensions.Enrichment v1.20.1-beta.1

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

  See CHANGELOG for details.

1.20.1-alpha.1

• NuGet: OpenTelemetry.Instrumentation.EventCounters v1.20.1-alpha.1

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

  See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.Runtime from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Instrumentation.Runtime's releases.

1.20.1

• NuGet: OpenTelemetry.Extensions.AWS v1.20.1

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

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Instrumentation.AWS v1.20.1

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.1

  No notable changes.

  See CHANGELOG for details.

1.20.1-rc.1

• NuGet: OpenTelemetry.Instrumentation.Process v1.20.1-rc.1

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

  See CHANGELOG for details.

1.20.1-beta.1

• NuGet: OpenTelemetry.Extensions.Enrichment v1.20.1-beta.1

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

  See CHANGELOG for details.

1.20.1-alpha.1

• NuGet: OpenTelemetry.Instrumentation.EventCounters v1.20.1-alpha.1

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

  See CHANGELOG for details.

Commits viewable in compare view.

Updated Scalar.AspNetCore from 2.18.0 to 2.18.3.

Release notes

Sourced from Scalar.AspNetCore's releases.

No release notes found for this version range.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!