Skip to content

chore: Bump Aspire.Hosting.AppHost and 13 others - #76

Merged
Tielem merged 1 commit into
devfrom
dependabot/nuget/dev/nuget-minor-and-patch-0de721071f
Sep 23, 2026
Merged

chore: Bump Aspire.Hosting.AppHost and 13 others#76
Tielem merged 1 commit into
devfrom
dependabot/nuget/dev/nuget-minor-and-patch-0de721071f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 23, 2026

Copy link
Copy Markdown
Contributor

Updated Aspire.Hosting.AppHost from 13.5.3 to 13.5.4.

Release notes

Sourced from Aspire.Hosting.AppHost's releases.

13.5.4

What's New in Aspire 13.5.4

Patch release for Aspire 13.5 that fixes Kafka health-check resource leaks, DevTunnel errors with automatically selected regions, misleading Azure emulator dashboard entries, and unintended changes to generated starter apps, plus Homebrew compatibility and Radius API diagnostic updates.

🐛 Fixes

  • 📨 Kafka health checks leaked producers and polling threads — Each AppHost health-check execution created a new Kafka producer without disposing it, accumulating background threads over time. Health checks now reuse a producer per Kafka resource and dispose it with the AppHost, while keeping multiple Kafka resources independently configured. Fixes #​20091. (#​20094, backport of #​20092, @​davidfowl)

  • 🌐 DevTunnels could fail when the region was selected automatically — Tunnel setup and health checks now use the cluster-qualified tunnel ID returned by the DevTunnel CLI for port operations and access queries. This fixes failures when a bare tunnel ID cannot be resolved for those operations. Regression introduced in 13.3. Fixes #​18790. (#​19853, backport of #​19230, @​Vladipz)

  • ☁️ Emulator-only AppHosts showed an unused Azure environment — The dashboard now hides the azure-environment resource when no Azure resources require cloud provisioning, instead of leaving it visible in Not started. It remains visible for apps that combine local emulators with resources requiring Azure provisioning. No AppHost changes are needed. Fixes #​19617. (#​19998, backport of #​19843, @​eerhardt)

  • 🧩 Starter app generation could alter unrelated JavaScript values — Dynamic port replacement could also replace matching numeric literals in bundled JavaScript, including Bootstrap timing values. Port substitutions are now restricted to localhost: URLs, preserving the original library files while still configuring the requested ports. Fixes #​20030. (#​20110, backport of #​20031, @​bart-vmware, @​JamesNK)

  • 🍎 Updated the Aspire Homebrew cask for Homebrew 6.x — Replaced deprecated cask URL and post-install syntax with the supported equivalents, resolving compatibility issues with current Homebrew while preserving install-channel metadata. (#​20119, backport of #​19965, @​askpt, @​joperezr)

  • 🧪 Radius cloud-provider callback interfaces now carry the experimental diagnostic — IAwsRadiusProviderBuilder and IAzureRadiusProviderBuilder are now marked with ASPIRERADIUS003, matching the existing WithAwsProvider and WithAzureProvider methods. Code referencing these interfaces directly must now acknowledge the same experimental API diagnostic. (#​19874, @​sebastienros)

Full Changelog: v13.5.3...v13.5.4

Full commit: 9c1b401dd67746739044f68959cbf4d3d7af93a6

Commits viewable in compare view.

Updated Aspire.Hosting.PostgreSQL from 13.5.3 to 13.5.4.

Release notes

Sourced from Aspire.Hosting.PostgreSQL's releases.

13.5.4

What's New in Aspire 13.5.4

Patch release for Aspire 13.5 that fixes Kafka health-check resource leaks, DevTunnel errors with automatically selected regions, misleading Azure emulator dashboard entries, and unintended changes to generated starter apps, plus Homebrew compatibility and Radius API diagnostic updates.

🐛 Fixes

  • 📨 Kafka health checks leaked producers and polling threads — Each AppHost health-check execution created a new Kafka producer without disposing it, accumulating background threads over time. Health checks now reuse a producer per Kafka resource and dispose it with the AppHost, while keeping multiple Kafka resources independently configured. Fixes #​20091. (#​20094, backport of #​20092, @​davidfowl)

  • 🌐 DevTunnels could fail when the region was selected automatically — Tunnel setup and health checks now use the cluster-qualified tunnel ID returned by the DevTunnel CLI for port operations and access queries. This fixes failures when a bare tunnel ID cannot be resolved for those operations. Regression introduced in 13.3. Fixes #​18790. (#​19853, backport of #​19230, @​Vladipz)

  • ☁️ Emulator-only AppHosts showed an unused Azure environment — The dashboard now hides the azure-environment resource when no Azure resources require cloud provisioning, instead of leaving it visible in Not started. It remains visible for apps that combine local emulators with resources requiring Azure provisioning. No AppHost changes are needed. Fixes #​19617. (#​19998, backport of #​19843, @​eerhardt)

  • 🧩 Starter app generation could alter unrelated JavaScript values — Dynamic port replacement could also replace matching numeric literals in bundled JavaScript, including Bootstrap timing values. Port substitutions are now restricted to localhost: URLs, preserving the original library files while still configuring the requested ports. Fixes #​20030. (#​20110, backport of #​20031, @​bart-vmware, @​JamesNK)

  • 🍎 Updated the Aspire Homebrew cask for Homebrew 6.x — Replaced deprecated cask URL and post-install syntax with the supported equivalents, resolving compatibility issues with current Homebrew while preserving install-channel metadata. (#​20119, backport of #​19965, @​askpt, @​joperezr)

  • 🧪 Radius cloud-provider callback interfaces now carry the experimental diagnostic — IAwsRadiusProviderBuilder and IAzureRadiusProviderBuilder are now marked with ASPIRERADIUS003, matching the existing WithAwsProvider and WithAzureProvider methods. Code referencing these interfaces directly must now acknowledge the same experimental API diagnostic. (#​19874, @​sebastienros)

Full Changelog: v13.5.3...v13.5.4

Full commit: 9c1b401dd67746739044f68959cbf4d3d7af93a6

Commits viewable in compare view.

Updated Aspire.Hosting.Testing from 13.5.3 to 13.5.4.

Release notes

Sourced from Aspire.Hosting.Testing's releases.

13.5.4

What's New in Aspire 13.5.4

Patch release for Aspire 13.5 that fixes Kafka health-check resource leaks, DevTunnel errors with automatically selected regions, misleading Azure emulator dashboard entries, and unintended changes to generated starter apps, plus Homebrew compatibility and Radius API diagnostic updates.

🐛 Fixes

  • 📨 Kafka health checks leaked producers and polling threads — Each AppHost health-check execution created a new Kafka producer without disposing it, accumulating background threads over time. Health checks now reuse a producer per Kafka resource and dispose it with the AppHost, while keeping multiple Kafka resources independently configured. Fixes #​20091. (#​20094, backport of #​20092, @​davidfowl)

  • 🌐 DevTunnels could fail when the region was selected automatically — Tunnel setup and health checks now use the cluster-qualified tunnel ID returned by the DevTunnel CLI for port operations and access queries. This fixes failures when a bare tunnel ID cannot be resolved for those operations. Regression introduced in 13.3. Fixes #​18790. (#​19853, backport of #​19230, @​Vladipz)

  • ☁️ Emulator-only AppHosts showed an unused Azure environment — The dashboard now hides the azure-environment resource when no Azure resources require cloud provisioning, instead of leaving it visible in Not started. It remains visible for apps that combine local emulators with resources requiring Azure provisioning. No AppHost changes are needed. Fixes #​19617. (#​19998, backport of #​19843, @​eerhardt)

  • 🧩 Starter app generation could alter unrelated JavaScript values — Dynamic port replacement could also replace matching numeric literals in bundled JavaScript, including Bootstrap timing values. Port substitutions are now restricted to localhost: URLs, preserving the original library files while still configuring the requested ports. Fixes #​20030. (#​20110, backport of #​20031, @​bart-vmware, @​JamesNK)

  • 🍎 Updated the Aspire Homebrew cask for Homebrew 6.x — Replaced deprecated cask URL and post-install syntax with the supported equivalents, resolving compatibility issues with current Homebrew while preserving install-channel metadata. (#​20119, backport of #​19965, @​askpt, @​joperezr)

  • 🧪 Radius cloud-provider callback interfaces now carry the experimental diagnostic — IAwsRadiusProviderBuilder and IAzureRadiusProviderBuilder are now marked with ASPIRERADIUS003, matching the existing WithAwsProvider and WithAzureProvider methods. Code referencing these interfaces directly must now acknowledge the same experimental API diagnostic. (#​19874, @​sebastienros)

Full Changelog: v13.5.3...v13.5.4

Full commit: 9c1b401dd67746739044f68959cbf4d3d7af93a6

Commits viewable in compare view.

Pinned Aspire.Npgsql at 13.5.4.

Release notes

Sourced from Aspire.Npgsql's releases.

13.5.4

What's New in Aspire 13.5.4

Patch release for Aspire 13.5 that fixes Kafka health-check resource leaks, DevTunnel errors with automatically selected regions, misleading Azure emulator dashboard entries, and unintended changes to generated starter apps, plus Homebrew compatibility and Radius API diagnostic updates.

🐛 Fixes

  • 📨 Kafka health checks leaked producers and polling threads — Each AppHost health-check execution created a new Kafka producer without disposing it, accumulating background threads over time. Health checks now reuse a producer per Kafka resource and dispose it with the AppHost, while keeping multiple Kafka resources independently configured. Fixes #​20091. (#​20094, backport of #​20092, @​davidfowl)

  • 🌐 DevTunnels could fail when the region was selected automatically — Tunnel setup and health checks now use the cluster-qualified tunnel ID returned by the DevTunnel CLI for port operations and access queries. This fixes failures when a bare tunnel ID cannot be resolved for those operations. Regression introduced in 13.3. Fixes #​18790. (#​19853, backport of #​19230, @​Vladipz)

  • ☁️ Emulator-only AppHosts showed an unused Azure environment — The dashboard now hides the azure-environment resource when no Azure resources require cloud provisioning, instead of leaving it visible in Not started. It remains visible for apps that combine local emulators with resources requiring Azure provisioning. No AppHost changes are needed. Fixes #​19617. (#​19998, backport of #​19843, @​eerhardt)

  • 🧩 Starter app generation could alter unrelated JavaScript values — Dynamic port replacement could also replace matching numeric literals in bundled JavaScript, including Bootstrap timing values. Port substitutions are now restricted to localhost: URLs, preserving the original library files while still configuring the requested ports. Fixes #​20030. (#​20110, backport of #​20031, @​bart-vmware, @​JamesNK)

  • 🍎 Updated the Aspire Homebrew cask for Homebrew 6.x — Replaced deprecated cask URL and post-install syntax with the supported equivalents, resolving compatibility issues with current Homebrew while preserving install-channel metadata. (#​20119, backport of #​19965, @​askpt, @​joperezr)

  • 🧪 Radius cloud-provider callback interfaces now carry the experimental diagnostic — IAwsRadiusProviderBuilder and IAzureRadiusProviderBuilder are now marked with ASPIRERADIUS003, matching the existing WithAwsProvider and WithAzureProvider methods. Code referencing these interfaces directly must now acknowledge the same experimental API diagnostic. (#​19874, @​sebastienros)

Full Changelog: v13.5.3...v13.5.4

Full commit: 9c1b401dd67746739044f68959cbf4d3d7af93a6

Commits viewable in compare view.

Pinned Aspire.Npgsql.EntityFrameworkCore.PostgreSQL at 13.5.4.

Release notes

Sourced from Aspire.Npgsql.EntityFrameworkCore.PostgreSQL's releases.

13.5.4

What's New in Aspire 13.5.4

Patch release for Aspire 13.5 that fixes Kafka health-check resource leaks, DevTunnel errors with automatically selected regions, misleading Azure emulator dashboard entries, and unintended changes to generated starter apps, plus Homebrew compatibility and Radius API diagnostic updates.

🐛 Fixes

  • 📨 Kafka health checks leaked producers and polling threads — Each AppHost health-check execution created a new Kafka producer without disposing it, accumulating background threads over time. Health checks now reuse a producer per Kafka resource and dispose it with the AppHost, while keeping multiple Kafka resources independently configured. Fixes #​20091. (#​20094, backport of #​20092, @​davidfowl)

  • 🌐 DevTunnels could fail when the region was selected automatically — Tunnel setup and health checks now use the cluster-qualified tunnel ID returned by the DevTunnel CLI for port operations and access queries. This fixes failures when a bare tunnel ID cannot be resolved for those operations. Regression introduced in 13.3. Fixes #​18790. (#​19853, backport of #​19230, @​Vladipz)

  • ☁️ Emulator-only AppHosts showed an unused Azure environment — The dashboard now hides the azure-environment resource when no Azure resources require cloud provisioning, instead of leaving it visible in Not started. It remains visible for apps that combine local emulators with resources requiring Azure provisioning. No AppHost changes are needed. Fixes #​19617. (#​19998, backport of #​19843, @​eerhardt)

  • 🧩 Starter app generation could alter unrelated JavaScript values — Dynamic port replacement could also replace matching numeric literals in bundled JavaScript, including Bootstrap timing values. Port substitutions are now restricted to localhost: URLs, preserving the original library files while still configuring the requested ports. Fixes #​20030. (#​20110, backport of #​20031, @​bart-vmware, @​JamesNK)

  • 🍎 Updated the Aspire Homebrew cask for Homebrew 6.x — Replaced deprecated cask URL and post-install syntax with the supported equivalents, resolving compatibility issues with current Homebrew while preserving install-channel metadata. (#​20119, backport of #​19965, @​askpt, @​joperezr)

  • 🧪 Radius cloud-provider callback interfaces now carry the experimental diagnostic — IAwsRadiusProviderBuilder and IAzureRadiusProviderBuilder are now marked with ASPIRERADIUS003, matching the existing WithAwsProvider and WithAzureProvider methods. Code referencing these interfaces directly must now acknowledge the same experimental API diagnostic. (#​19874, @​sebastienros)

Full Changelog: v13.5.3...v13.5.4

Full commit: 9c1b401dd67746739044f68959cbf4d3d7af93a6

Commits viewable in compare view.

Pinned Dapr.AspNetCore at 1.18.8.

Release notes

Sourced from Dapr.AspNetCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Pinned Dapr.Workflow at 1.18.8.

Release notes

Sourced from Dapr.Workflow's releases.

No release notes found for this version range.

Commits viewable in compare view.

Pinned Jint at 4.16.3.

Release notes

Sourced from Jint's releases.

4.16.3

Jint 4.16.3 is a maintenance release from the 4.x branch: correctness and conformance fixes backported from main, and nothing that changes an existing API or an existing default. If you are on 4.16.2 it is a drop-in update — every public signature is the one 4.16.0 shipped, on all five target frameworks, and the per-framework snapshots in Jint.Tests.PublicInterface/Verify/ are unchanged. main remains 5.0.0 development; what is coming there is recorded as it lands in docs/v5-migration.md.

Highlights

A long-lived engine stops accumulating what it has already run. Evaluate(string) and Execute(string) parse a fresh Script on every call, and the engine kept every one of them. Three of the four per-engine handler-tree caches already reset wholesale at 2048 entries so a host streaming endless distinct sources cannot grow them without bound; the fourth, _evaluatedScripts, never got that ceiling and held its keys strongly, retaining the AST of every distinct script the engine had ever evaluated — about 528 bytes per call, climbing forever and reclaimed by nothing short of dropping the engine (#​4116). The realm's tagged-template map had the same shape and a harder constraint: Realm._templateMap was a Dictionary<Node, JsArray>, strong on both ends and never cleared, costing roughly 1.35 KB per call for a frozen array and its raw array. A ceiling is no remedy there, because evicting a live template site is script-visible — f() === f() must hold for one site — so it becomes a ConditionalWeakTable<Node, WeakReference<JsArray>>, weak on both halves (#​4119). Both matter most to exactly the embedding that looks innocuous: one engine, kept for the lifetime of the process, handed ad-hoc source.

A suspended frame no longer dereferences what the suspension produced. await and yield suspend by returning a plain undefined, and the enclosing member link turns that into a sentinel reference that every consumer must recognise before reading. Nine did not, so they read undefined.undefined and raised a TypeError inside a frame that was already suspended. AsyncBlockStart swallowed that throw, but not before the statement-list resume position had been cleared on the way out — so the resume replayed the body from the first statement: one extra run of every un-awaited side effect per suspension point, and a re-entrancy guard silently truncating the rest. In a generator nothing swallows it and the TypeError comes straight out of next(). Two shapes were wrong answers rather than repeated ones — (await p).x = 1 rejected the promise, and o[await k] = 1 assigned to the literal key "undefined" instead of the real one — and for await ((await p).a of it) never terminated at all. Optional chaining was not the trigger despite where the report put it: the guarded fast lane needs a literal property name, so every computed member read of an awaited or yielded value fell through, (await p)[0] as much as (await p)[k] (#​4089, reported by @​davidwengier in #​4086).

Verification

Every change was verified failing-first against the unfixed branch. The suspension fix is pinned by 35 new cases in Jint.Tests/Runtime/SuspendedOptionalChainTests.cs: against 4.16.2's code 28 fail and 6 pass on both .NET 10 and .NET Framework 4.7.2, with a 35th — the for await shape — hanging the test host outright rather than failing; after the fix all 35 pass on both. The retention fixes are pinned by Jint.Tests/Runtime/GarbageCollectionTests.cs and TaggedTemplateCacheTests.cs.

Release diagnostics on the tagged commit, in Release: Jint.Tests 7,170 (net10.0) and 7,085 (net472); Jint.Tests.PublicInterface 1,852 and 1,844; Jint.Tests.CommonScripts 28 and 28; Jint.Tests.SourceGenerators 52; the host-contract verification leg (JINT_HOST_CONTRACT_VERIFICATION=1) 7,170 / 7,085 and 1,856 / 1,848 — zero failures anywhere. test262: 102,498 passed, 183 skipped, with three files crossing the engine's default 30-second budget under whole-suite CPU contention and passing in three seconds when run alone.

The paired SunSpider and Dromaeo comparison against 4.16.2 was run after the tag rather than before it, which is a departure from how 4.16.2 was gated; it is recorded here because the result is what the release notes should carry, not the order it arrived in. No row regressed. Fifty-one rows, paired, alternating order, DefaultJob, on an idle machine: the three-round screen left two candidates clearing the sign-agreement and magnitude bar, both of them Dromaeo.StringBase64, and re-measuring those at eight rounds read −1.72% [−3.01, +1.98] and +0.30% [−3.10, +4.26] — no change, with a third parameter combination coming out faster. StringBase64 is the row Jint.Benchmark/AGENTS.md already documents as a three-round false positive, and it behaved as documented. The Cube control rows moved +0.6% to +0.8%, which is this machine's floor on rows the change cannot reach.

Nothing here is a performance change by intent. #​4119 does move a tagged-template lookup from a Dictionary to a ConditionalWeakTable and #​4089 adds suspension checks to several interpreter lanes, and neither is visible above the noise floor.

What's Changed

Full Changelog: sebastienros/jint@v4.16.2...v4.16.3

Commits viewable in compare view.

Pinned OpenTelemetry.Exporter.OpenTelemetryProtocol at 1.19.1.

Release notes

Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.

1.19.1

For highlights and announcements pertaining to this release see: Release Notes > 1.19.1.

The following changes are from the previous release 1.19.0.

1.19.1-rc.1

The following changes are from the previous release 1.19.0.

1.19.1-beta.1

The following changes are from the previous release 1.19.0-beta.1.

1.19.0

For highlights and announcements pertaining to this release see: Release Notes > 1.19.0.

The following changes are from the previous release 1.18.0.

  • NuGet: OpenTelemetry v1.19.0

    • Added Schema URL to internally created Resource instances.
      (#​7726)

    • Reduced allocations when formatting self-diagnostics events with up to three parameters.
      (#​7730)

    • Added AlwaysRecordSampler.
      (#​7695)

    • Fixed CircularBufferBuckets so the first delta histogram insertion after a reset does not result in an unnecessary scale reduction.
      (#​7749)

    • Improved wildcard source/meter name matching to avoid excessive matching time at runtime.
      (#​7760)

    • Fixed lazy logger provider builds after a failure from reusing partially initialized provider state.
      (#​7761)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.19.0

    • Reduced allocations when creating log record attributes from an array.
      (#​7699)

    • Reduced allocations when setting baggage through the params overload.
      (#​7697)

    • Reduced allocations when constructing SpanAttributes from an array.
      (#​7698)

    • Fixed parsing of an inbound tracestate header whose member value trimmed to an empty value that previously threw an IndexOutOfRangeException internally and could silently truncate the tracestate.
      (#​7756)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.0

    No notable changes.

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Console v1.19.0

... (truncated)

1.19.0-rc.1

The following changes are from the previous release 1.18.0.

  • NuGet: OpenTelemetry v1.19.0-rc.1

    • Added Schema URL to internally created Resource instances.
      (#​7726)

    • Reduced allocations when formatting self-diagnostics events with up to three parameters.
      (#​7730)

    • Added AlwaysRecordSampler.
      (#​7695)

    • Fixed CircularBufferBuckets so the first delta histogram insertion after a reset does not result in an unnecessary scale reduction.
      (#​7749)

    • Improved wildcard source/meter name matching to avoid excessive matching time at runtime.
      (#​7760)

    • Fixed lazy logger provider builds after a failure from reusing partially initialized provider state.
      (#​7761)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.19.0-rc.1

    • Reduced allocations when creating log record attributes from an array.
      (#​7699)

    • Reduced allocations when setting baggage through the params overload.
      (#​7697)

    • Reduced allocations when constructing SpanAttributes from an array.
      (#​7698)

    • Fixed parsing of an inbound tracestate header whose member value trimmed to an empty value that previously threw an IndexOutOfRangeException internally and could silently truncate the tracestate.
      (#​7756)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.0-rc.1

    No notable changes.

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Console v1.19.0-rc.1

    • Extended key/value list attribute handling to cover additional dictionary shapes (IEnumerable<KeyValuePair<string, string?>> and IDictionary). These attributes will be serialized as JSON objects.
      (#​7679)
      ... (truncated)

1.19.0-beta.1

The following changes are from the previous release 1.18.0-beta.1.

  • NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.19.0-beta.1

    • Breaking Change The PrometheusTranslationStrategy enum was renamed to PrometheusAspNetCoreTranslationStrategy.
      (#​7751)

    • Fixed OpenMetrics _created series being emitted for metric points with a default start time.
      (#​7754)

    • Prometheus text/OpenMetrics escaping of label values, label names and help text is now more efficient.
      (#​7758)

    • A scrape request whose connection is aborted, or whose X-Prometheus-Scrape-Timeout-Seconds deadline elapses, now stops waiting for an in-progress metrics collection instead of continuing to wait for it to finish. The collection itself is not cancelled and continues running in the background.
      (#​7757)

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.19.0-beta.1

    • Breaking Change The PrometheusTranslationStrategy enum was renamed to PrometheusHttpListenerTranslationStrategy.
      (#​7751)

    • Fixed OpenMetrics _created series being emitted for metric points with a default start time.
      (#​7754)

    • Prometheus text/OpenMetrics escaping of label values, label names and help text is now more efficient.
      (#​7758)

    • Added PrometheusHttpListenerOptions.ScrapeResponseTimeoutMilliseconds (default 60000) which bounds how long a scrape request waits for its response. X-Prometheus-Scrape-Timeout-Seconds request header values may only shorten this limit. The limit bounds the request's wait only: a metrics collection already running when it is reached is not cancelled and continues running in the background.
      (#​7757)

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Shims.OpenTracing v1.19.0-beta.1

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

Commits viewable in compare view.

Pinned OpenTelemetry.Extensions.Hosting at 1.19.1.

Release notes

Sourced from OpenTelemetry.Extensions.Hosting's releases.

1.19.1

For highlights and announcements pertaining to this release see: Release Notes > 1.19.1.

The following changes are from the previous release 1.19.0.

1.19.1-rc.1

The following changes are from the previous release 1.19.0.

1.19.1-beta.1

The following changes are from the previous release 1.19.0-beta.1.

1.19.0

For highlights and announcements pertaining to this release see: Release Notes > 1.19.0.

The following changes are from the previous release 1.18.0.

  • NuGet: OpenTelemetry v1.19.0

    • Added Schema URL to internally created Resource instances.
      (#​7726)

    • Reduced allocations when formatting self-diagnostics events with up to three parameters.
      (#​7730)

    • Added AlwaysRecordSampler.
      (#​7695)

    • Fixed CircularBufferBuckets so the first delta histogram insertion after a reset does not result in an unnecessary scale reduction.
      (#​7749)

    • Improved wildcard source/meter name matching to avoid excessive matching time at runtime.
      (#​7760)

    • Fixed lazy logger provider builds after a failure from reusing partially initialized provider state.
      (#​7761)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.19.0

    • Reduced allocations when creating log record attributes from an array.
      (#​7699)

    • Reduced allocations when setting baggage through the params overload.
      (#​7697)

    • Reduced allocations when constructing SpanAttributes from an array.
      (#​7698)

    • Fixed parsing of an inbound tracestate header whose member value trimmed to an empty value that previously threw an IndexOutOfRangeException internally and could silently truncate the tracestate.
      (#​7756)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.0

    No notable changes.

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Console v1.19.0

... (truncated)

1.19.0-rc.1

The following changes are from the previous release 1.18.0.

  • NuGet: OpenTelemetry v1.19.0-rc.1

    • Added Schema URL to internally created Resource instances.
      (#​7726)

    • Reduced allocations when formatting self-diagnostics events with up to three parameters.
      (#​7730)

    • Added AlwaysRecordSampler.
      (#​7695)

    • Fixed CircularBufferBuckets so the first delta histogram insertion after a reset does not result in an unnecessary scale reduction.
      (#​7749)

    • Improved wildcard source/meter name matching to avoid excessive matching time at runtime.
      (#​7760)

    • Fixed lazy logger provider builds after a failure from reusing partially initialized provider state.
      (#​7761)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.19.0-rc.1

    • Reduced allocations when creating log record attributes from an array.
      (#​7699)

    • Reduced allocations when setting baggage through the params overload.
      (#​7697)

    • Reduced allocations when constructing SpanAttributes from an array.
      (#​7698)

    • Fixed parsing of an inbound tracestate header whose member value trimmed to an empty value that previously threw an IndexOutOfRangeException internally and could silently truncate the tracestate.
      (#​7756)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.0-rc.1

    No notable changes.

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Console v1.19.0-rc.1

    • Extended key/value list attribute handling to cover additional dictionary shapes (IEnumerable<KeyValuePair<string, string?>> and IDictionary). These attributes will be serialized as JSON objects.
      (#​7679)
      ... (truncated)

1.19.0-beta.1

The following changes are from the previous release 1.18.0-beta.1.

  • NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.19.0-beta.1

    • Breaking Change The PrometheusTranslationStrategy enum was renamed to PrometheusAspNetCoreTranslationStrategy.
      (#​7751)

    • Fixed OpenMetrics _created series being emitted for metric points with a default start time.
      (#​7754)

    • Prometheus text/OpenMetrics escaping of label values, label names and help text is now more efficient.
      (#​7758)

    • A scrape request whose connection is aborted, or whose X-Prometheus-Scrape-Timeout-Seconds deadline elapses, now stops waiting for an in-progress metrics collection instead of continuing to wait for it to finish. The collection itself is not cancelled and continues running in the background.
      (#​7757)

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.19.0-beta.1

    • Breaking Change The PrometheusTranslationStrategy enum was renamed to PrometheusHttpListenerTranslationStrategy.
      (#​7751)

    • Fixed OpenMetrics _created series being emitted for metric points with a default start time.
      (#​7754)

    • Prometheus text/OpenMetrics escaping of label values, label names and help text is now more efficient.
      (#​7758)

    • Added PrometheusHttpListenerOptions.ScrapeResponseTimeoutMilliseconds (default 60000) which bounds how long a scrape request waits for its response. X-Prometheus-Scrape-Timeout-Seconds request header values may only shorten this limit. The limit bounds the request's wait only: a metrics collection already running when it is reached is not cancelled and continues running in the background.
      (#​7757)

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Shims.OpenTracing v1.19.0-beta.1

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

Commits viewable in compare view.

Pinned OpenTelemetry.Instrumentation.AspNetCore at 1.19.0.

Release notes

Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.

1.19.0

1.19.0-rc.1

1.19.0-beta.1

1.19.0-alpha.1

1.18.1

_Description has been tru...

Description has been truncated

@dependabot
chore: Bump Aspire.Hosting.AppHost and 13 others
14e7cdb 
Bumps Aspire.Hosting.AppHost from 13.5.3 to 13.5.4
Bumps Aspire.Hosting.PostgreSQL from 13.5.3 to 13.5.4
Bumps Aspire.Hosting.Testing from 13.5.3 to 13.5.4
Bumps Aspire.Npgsql from 13.5.3 to 13.5.4
Bumps Aspire.Npgsql.EntityFrameworkCore.PostgreSQL from 13.5.3 to 13.5.4
Bumps Dapr.AspNetCore from 1.18.7 to 1.18.8
Bumps Dapr.Workflow from 1.18.7 to 1.18.8
Bumps Jint from 4.16.2 to 4.16.3
Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.18.0 to 1.19.1
Bumps OpenTelemetry.Extensions.Hosting from 1.18.0 to 1.19.1
Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.18.0 to 1.19.0
Bumps OpenTelemetry.Instrumentation.Http from 1.18.0 to 1.19.0
Bumps OpenTelemetry.Instrumentation.Runtime from 1.18.0 to 1.19.0
Bumps WireMock.Net from 2.15.0 to 2.18.0

---
updated-dependencies:
- dependency-name: Aspire.Hosting.AppHost
  dependency-version: 13.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-and-patch
- dependency-name: Aspire.Hosting.PostgreSQL
  dependency-version: 13.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-and-patch
- dependency-name: Aspire.Hosting.Testing
  dependency-version: 13.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-and-patch
- dependency-name: Aspire.Npgsql
  dependency-version: 13.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-and-patch
- dependency-name: Aspire.Npgsql.EntityFrameworkCore.PostgreSQL
  dependency-version: 13.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-and-patch
- dependency-name: Dapr.AspNetCore
  dependency-version: 1.18.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-and-patch
- dependency-name: Dapr.Workflow
  dependency-version: 1.18.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-and-patch
- dependency-name: Jint
  dependency-version: 4.16.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-minor-and-patch
- dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol
  dependency-version: 1.19.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-and-patch
- dependency-name: OpenTelemetry.Extensions.Hosting
  dependency-version: 1.19.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-and-patch
- dependency-name: OpenTelemetry.Instrumentation.AspNetCore
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-and-patch
- dependency-name: OpenTelemetry.Instrumentation.Http
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-and-patch
- dependency-name: OpenTelemetry.Instrumentation.Runtime
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-and-patch
- dependency-name: WireMock.Net
  dependency-version: 2.18.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Sep 23, 2026
@Tielem
Tielem merged commit b0030fb into dev Sep 23, 2026
1 check passed
@Tielem
Tielem deleted the dependabot/nuget/dev/nuget-minor-and-patch-0de721071f branch September 23, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Tielem