Repository navigation
Bump Aspire.Hosting.Docker and 25 others - #25
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Aspire.Hosting.Docker from 13.6.0 to 13.6.4 Bumps Aspire.Hosting.JavaScript from 13.6.0 to 13.6.4 Bumps Aspire.Hosting.PostgreSQL from 13.6.0 to 13.6.4 Bumps Aspire.Hosting.Valkey from 13.6.0 to 13.6.4 Bumps MessagePack from 2.5.303 to 2.5.307 Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.11 to 10.0.14 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.1 to 10.0.14 Bumps Microsoft.AspNetCore.OpenApi from 10.0.11 to 10.0.14 Bumps Microsoft.EntityFrameworkCore from 10.0.4 to 10.0.14 Bumps Microsoft.EntityFrameworkCore.Design from 10.0.4 to 10.0.14 Bumps Microsoft.EntityFrameworkCore.InMemory from 10.0.4 to 10.0.14 Bumps Microsoft.Extensions.ApiDescription.Server from 10.0.11 to 10.0.14 Bumps Microsoft.Extensions.Caching.Hybrid from 10.1.0 to 10.11.0 Bumps Microsoft.Extensions.Configuration.UserSecrets from 10.0.12 to 10.0.14 Bumps Microsoft.Extensions.Http from 10.0.12 to 10.0.14 Bumps Microsoft.Extensions.Http.Resilience from 10.1.0 to 10.11.0 Bumps Microsoft.Extensions.Options.ConfigurationExtensions from 10.0.4 to 10.0.14 Bumps Microsoft.Extensions.ServiceDiscovery from 10.1.0 to 10.11.0 Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol to 1.20.1 Bumps OpenTelemetry.Extensions.Hosting from 1.17.0 to 1.20.1 Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.18.0 to 1.20.1 Bumps OpenTelemetry.Instrumentation.Http from 1.18.0 to 1.20.1 Bumps OpenTelemetry.Instrumentation.Runtime from 1.18.0 to 1.20.1 Bumps StackExchange.Redis from 2.13.1 to 2.13.17 Bumps System.IdentityModel.Tokens.Jwt from 8.19.2 to 8.23.0 Bumps xunit.v3.mtp-v2 from 4.0.1 to 4.0.2 --- updated-dependencies: - dependency-name: Aspire.Hosting.Docker dependency-version: 13.6.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: MessagePack dependency-version: 2.5.307 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Aspire.Hosting.JavaScript dependency-version: 13.6.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Aspire.Hosting.PostgreSQL dependency-version: 13.6.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Aspire.Hosting.Valkey dependency-version: 13.6.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.AspNetCore.OpenApi dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.EntityFrameworkCore dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.EntityFrameworkCore.Design dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.Extensions.ApiDescription.Server dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.Extensions.Caching.Hybrid dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: Microsoft.Extensions.Configuration.UserSecrets dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.Extensions.Http dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: Microsoft.Extensions.Options.ConfigurationExtensions dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.Extensions.ServiceDiscovery dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: OpenTelemetry.Instrumentation.AspNetCore dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: OpenTelemetry.Instrumentation.Http dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: OpenTelemetry.Instrumentation.Runtime dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: StackExchange.Redis dependency-version: 2.13.17 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: xunit.v3.mtp-v2 dependency-version: 4.0.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: xunit.v3.mtp-v2 dependency-version: 4.0.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: Microsoft.EntityFrameworkCore.InMemory dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: System.IdentityModel.Tokens.Jwt dependency-version: 8.23.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: System.IdentityModel.Tokens.Jwt dependency-version: 8.23.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-compatible - dependency-name: xunit.v3.mtp-v2 dependency-version: 4.0.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-compatible ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Superseded by #36. |
dependabot
Bot
deleted the
dependabot/nuget/src/ShutterSpool.AppHost/nuget-compatible-a65f692898
branch
November 8, 2026 05:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Aspire.Hosting.Docker from 13.6.0 to 13.6.4.
Release notes
Sourced from Aspire.Hosting.Docker'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
FailedToStartstate 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 throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher: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 use0700; 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
Full Changelog: microsoft/aspire@v13.6.1...v13.6.2
13.6.1
What's New in Aspire 13.6.1
Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.
🐛 Fixes
📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #20725. (#20747, backport of #20736, @JamesNK)
📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #20728. (#20762, backport of #20758, @heyysiri)
🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#20545, backport of #20527, @JamesNK)
🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical
Watch task over Kubernetes ContainerExec resources terminated unexpectedlyerror and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#20664, backport of #20466, @radical)🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through
dotnet runordotnet watchnow allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C andaspire stopflows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #20495. (#20514, backport of #20494, @danegsta)Full Changelog: v13.6.0...v13.6.1
Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8
Commits viewable in compare view.
Updated Aspire.Hosting.JavaScript from 13.6.0 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
FailedToStartstate 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 throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher: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 use0700; 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
Full Changelog: microsoft/aspire@v13.6.1...v13.6.2
13.6.1
What's New in Aspire 13.6.1
Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.
🐛 Fixes
📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #20725. (#20747, backport of #20736, @JamesNK)
📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #20728. (#20762, backport of #20758, @heyysiri)
🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#20545, backport of #20527, @JamesNK)
🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical
Watch task over Kubernetes ContainerExec resources terminated unexpectedlyerror and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#20664, backport of #20466, @radical)🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through
dotnet runordotnet watchnow allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C andaspire stopflows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #20495. (#20514, backport of #20494, @danegsta)Full Changelog: v13.6.0...v13.6.1
Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8
Commits viewable in compare view.
Updated Aspire.Hosting.PostgreSQL from 13.6.0 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
FailedToStartstate 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 throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher: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 use0700; 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
Full Changelog: microsoft/aspire@v13.6.1...v13.6.2
13.6.1
What's New in Aspire 13.6.1
Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.
🐛 Fixes
📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #20725. (#20747, backport of #20736, @JamesNK)
📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #20728. (#20762, backport of #20758, @heyysiri)
🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#20545, backport of #20527, @JamesNK)
🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical
Watch task over Kubernetes ContainerExec resources terminated unexpectedlyerror and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#20664, backport of #20466, @radical)🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through
dotnet runordotnet watchnow allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C andaspire stopflows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #20495. (#20514, backport of #20494, @danegsta)Full Changelog: v13.6.0...v13.6.1
Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8
Commits viewable in compare view.
Updated Aspire.Hosting.Valkey from 13.6.0 to 13.6.4.
Release notes
Sourced from Aspire.Hosting.Valkey'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
FailedToStartstate 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 throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher: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 use0700; 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
Full Changelog: microsoft/aspire@v13.6.1...v13.6.2
13.6.1
What's New in Aspire 13.6.1
Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.
🐛 Fixes
📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #20725. (#20747, backport of #20736, @JamesNK)
📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #20728. (#20762, backport of #20758, @heyysiri)
🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#20545, backport of #20527, @JamesNK)
🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical
Watch task over Kubernetes ContainerExec resources terminated unexpectedlyerror and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#20664, backport of #20466, @radical)🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through
dotnet runordotnet watchnow allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C andaspire stopflows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #20495. (#20514, backport of #20494, @danegsta)Full Changelog: v13.6.0...v13.6.1
Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8
Commits viewable in compare view.
Updated MessagePack from 2.5.303 to 2.5.307.
Release notes
Sourced from MessagePack's releases.
2.5.307
Security fix
Full Changelog: MessagePack-CSharp/MessagePack-CSharp@v2.5.305...v2.5.307
2.5.305
Security fix
Full Changelog: MessagePack-CSharp/MessagePack-CSharp@v2.5.303...v2.5.305
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.11 to 10.0.14.
Release notes
Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Mvc.Testing from 10.0.1 to 10.0.14.
Release notes
Sourced from Microsoft.AspNetCore.Mvc.Testing's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.OpenApi from 10.0.11 to 10.0.14.
Release notes
Sourced from Microsoft.AspNetCore.OpenApi's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore from 10.0.4 to 10.0.14.
Release notes
Sourced from Microsoft.EntityFrameworkCore's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.Design from 10.0.4 to 10.0.14.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Design's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.InMemory from 10.0.4 to 10.0.14.
Release notes
Sourced from Microsoft.EntityFrameworkCore.InMemory's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.ApiDescription.Server from 10.0.11 to 10.0.14.
Release notes
Sourced from Microsoft.Extensions.ApiDescription.Server's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Caching.Hybrid from 10.1.0 to 10.11.0.
Release notes
Sourced from Microsoft.Extensions.Caching.Hybrid's releases.
10.11.0
.NET Extensions 10.11.0
This release adds optional scope capture for buffered logs and updates experimental HTTP latency enrichment APIs. It also includes fixes for AI streaming and function invocation, evaluation reports, HybridCache invalidation, and logging.
Experimental API Changes
New Experimental APIs
GlobalLogBufferingOptions.IncludeScopesandPerRequestLogBufferingOptions.IncludeScopes(EXTEXP0003) #7813Breaking Changes to Experimental APIs
AddHttpLatencyTelemetryis renamed toAddHttpServerLatencyTelemetryand moves fromHttpLatencyTelemetryServiceCollectionExtensionstoHttpLoggingServiceCollectionExtensions. It remains experimental underEXTEXP0013in this release. #7730What's Changed
AI
AI Evaluation
Telemetry and Observability
ASP.NET Core Extensions
AI Project Templates
Caching
... (truncated)
10.10.1
This release fixes two OpenAI integration issues: a TypeLoadException on tool-carrying Responses API calls and a streaming crash against third-party OpenAI-compatible endpoints, by upgrading the OpenAI SDK to 2.14.0.
Packages in this release
10.10.110.10.1What's Changed
AI
Acknowledgements
Full Changelog: dotnet/extensions@v10.10.0...v10.10.1
10.10.0
This month's release focuses on AI package reliability: closing gaps in evaluation scoring, hardening OpenAI image-option handling, and removing the deprecated OpenAI Assistants API support.
Experimental API Changes
Removed Experimental APIs
OPENAI001) #7724What's Changed
AI
AI Evaluation
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.9.0...v10.10.0
10.9.0
Version 10.9.0 is headlined by changes in these areas:
RoutingChatClientbase class, withSemanticRoutingChatClientas a concrete semantic-routing implementation. Separately, the abstractFailoverChatClientspecialization and its concreteOrderedFailoverChatClientimplementation add failover routing.Experimental API Changes
New Experimental APIs
EXTEXP0013) #7602MEAI001) #7662What's Changed
AI (
Microsoft.Extensions.AI,Microsoft.Extensions.AI.Abstractions, andMicrosoft.Extensions.AI.OpenAI)Note: Microsoft.Extensions.AI.OpenAI constrains its dependency for OpenAI to 2.12.x, preventing OpenAI updates to 2.13.0+ due to an incompatibility. We expect to release Microsoft.Extensions.AI.OpenAI version 10.9.1 during the week of August 17 to address this issue.
HTTP Resilience and Diagnostics (
Microsoft.Extensions.Http.ResilienceandMicrosoft.Extensions.Http.Diagnostics)ASP.NET Core Extensions (
Microsoft.AspNetCore.Diagnostics.Middleware)Logging Source Generator (
Microsoft.Gen.Logging)AI Evaluation (
Microsoft.Extensions.AI.Evaluation.Reporting)Project Templates (
Microsoft.McpServer.ProjectTemplates)... (truncated)
10.8.4
This servicing update refreshes the .NET AI project templates ahead of the July 30, 2026 retirement of GitHub Models — removing the GitHub Models provider option and updating template dependencies.
As a result, both the AI Chat Web (
aichatweb) and AI Agent Web API (aiagent-webapi) templates now require the AI service provider to be chosen explicitly via--provider; there is no longer a default. One of the following must be selected:--provider azureopenai— Azure OpenAI--provider ollama— Ollama (for local development)--provider openai— OpenAI PlatformPackages in this release
What's Changed
Project templates
--provideroption is now required with no default (#7667).Aspire.Hosting.AppHostto13.4.6andCommunityToolkit.VectorData.SqliteVecto1.0.0-preview.4(alignedSystem.Linq.AsyncEnumerableto10.0.9), replacing earlier workaround package pins (#7639).Full Changelog
10.8.3
Packages in this release
Experimental API Changes
Experimental API behavior updates
ToolApprovalRequestContent.RequiresConfirmationso it no longer leaks into consumer source-generatedAIContentJSON metadata unless approval APIs are intentionally used (#7659).What's Changed
AI abstractions and serialization
RequiresConfirmationin source-generatedAIContentcontexts by using an internal JSON-included backing member while keeping the public experimental member ignored for source-generation metadata (#7659).Test Improvements
List<AIContent>contexts compile and round-trip without requiring MEAI001 suppression (#7659).Full Changelog
10.8.2
This servicing release updates Microsoft.Extensions.VectorData.ConformanceTests to 10.8.2 and includes targeted test framework migration fixes.
Packages in this release
Update: August 7, 2026
The Microsoft.Extensions.VectorData.Abstractions package was initially excluded from this release by mistake. Because Microsoft.Extensions.VectorData.ConformanceTests has a dependency on Microsoft.Extensions.VectorData.Abstractions, that led to failures when updating to Microsoft.Extensions.VectorData.ConformanceTests 10.8.2.
Microsoft.Extensions.VectorData.Abstractions was published August 7, 2026 to resolve that issue.
What's Changed
AI
Acknowledgements
Full Changelog: dotnet/extensions@v10.8.1...v10.8.2
10.8.1
This servicing release updates the Microsoft.Extensions.AI, Microsoft.Extensions.AI.Abstractions, and Microsoft.Extensions.AI.OpenAI packages to 10.8.1 with two targeted fixes: correct tool-call/tool-result ordering when resuming approval-gated functions with service-managed chat history, and preservation of the OpenAI Responses reasoning item id for stateless (store=false) encrypted reasoning.
Packages in this release
What's Changed
AI
Acknowledgements
Full Changelog: dotnet/extensions@v10.8.0...v10.8.1
10.8.0
This release adds new experimental APIs to Microsoft.Extensions.AI.Abstractions and updates the OpenAI dependency to 2.12.0, alongside documentation, test, and repository maintenance.
Experimental API Changes
New Experimental APIs
AIFunctionNameAttributeandAIParameterNameAttribute#7610 by @jozkee (co-authored by @jeffhandley @Copilot)ToolApprovalRequestContent.RequiresConfirmation(MEAI001) #7549 by @javiercn (co-authored by @Copilot)What's Changed
AI
Vector Data
Documentation Updates
Test Improvements
Repository Infrastructure Updates
... (truncated)
10.7.0
v10.7.0 graduates the Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package to stable. The package registers a Kubernetes-aware
ResourceQuotaProviderthat reads the pod's CPU and memory requests and limits and exposes them toMicrosoft.Extensions.Diagnostics.ResourceMonitoringas baseline and maximum quotas, which then feed the request and limit dimensions of the published resource utilization metrics. The companionResourceQuotaandResourceQuotaProvidertypes inMicrosoft.Extensions.Diagnostics.ResourceMonitoringgraduate to stable in the same change so that consumers can implement custom quota providers without taking an experimental dependency.On the AI side,
Microsoft.Extensions.AI.OpenAImoves to OpenAI 2.11.0 and fixes a deserialization bug inToolJson.AdditionalPropertiesso that JSON SchemaadditionalPropertiesvalues shaped as sub-schema objects (for example{"type":"string"}) are preserved instead of throwing during deserialization.HostedFileContent.SizeInBytesandHostedFileContent.CreatedAtgraduate to stable since both values are consistently available across hosted-file providers, whilePurposeandScoperemain experimental as provider-shaped vocabulary.FunctionInvokingChatClientdrops a backward-compat path that auto-markedToolApprovalResponseContententries withInformationalOnly: true; consumers that need to continue accepting sessions serialized before #7468 can use the sampleApprovalHistoryNormalizingChatClientmiddleware added in the test project.Experimental API Changes
Now Stable
Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetespackage is now stable #7253ResourceQuotaandResourceQuotaProviderAPIs are now stable (previouslyEXTEXP0008) #7253HostedFileContent.SizeInBytesandHostedFileContent.CreatedAtare now stable (previouslyMEAI001) #7513What's Changed
AI
Diagnostics, Health Checks, and Resource Monitoring
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.6.0...v10.7.0
10.6.0
Version 10.6.0 stabilizes the response continuation token and background-response APIs in Microsoft.Extensions.AI.Abstractions. Most other AI work for May shipped in 10.5.1; this monthly release rolls those changes up alongside dependency updates and a small Resource Monitoring cleanup.
Experimental API Changes
Now Stable
MEAI001) #7512What's Changed
AI
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.5.2...v10.6.0
10.5.2
This patch release ships a single fix to
Microsoft.Extensions.VectorData.Abstractions, correctingStorageNameresolution when external serialization is enabled.Microsoft.Extensions.VectorData.ConformanceTests,Microsoft.Extensions.AI.Abstractions,Microsoft.Extensions.AI, andMicrosoft.Extensions.AI.OpenAIare published alongside it for version coherency — they contain no code changes from 10.5.1.Packages in this release
What's Changed
Microsoft.Extensions.VectorData.Abstractions
StorageNamebehavior when external serialization is enabled, and disable a warning fornet462. (by @roji in #7475)Full Changelog: dotnet/extensions@v10.5.1...v10.5.2
10.5.1
Version 10.5.1 of the Microsoft.Extensions.AI packages stabilizes CodeInterpreter, WebSearch, and ImageGeneration tool content types. The release adds new experimental tool search and OpenAI request policy hooks. And the OpenTelemetry gen-ai semantic conventions are updated to align with v1.41.
The 'aiagent-webapi' project template in Microsoft.Agents.AI.ProjectTemplates is updated to align with v1.3.0 of Agent Framework, updating the OpenTelemetry dependencies within the template projects as well.
Packages in this release
Experimental API Changes
Now Stable
The following types previously emitted the
MEAI001experimental diagnostic and are now stable.CodeInterpreterToolCallContentCodeInterpreterToolResultContentWebSearchToolCallContentWebSearchToolResultContentImageGenerationToolCallContentImageGenerationToolResultContentHostedImageGenerationToolImageGenerationOptionsImageGenerationResponseFormat(theHostedenum value remains experimental)IImageGeneratorand the rest of the image generation infrastructure also remain experimentalNew Experimental APIs
The following new APIs emit the
MEAI001experimental diagnostic.HostedToolSearchToolwithDeferredToolsfor tool-search-driven deferred tool loading #7471OpenAIRequestPoliciesextension hook for appendingSystem.ClientModel.PipelinePolicyinstances to outgoing OpenAI requests #7495Breaking Changes to Experimental APIs
WebSearchToolResultContent.Resultswas renamed toOutputsas part of the stabilization in #7493, aligning withCodeInterpreterToolResultContent.Outputs. The originalResultsproperty was included in version 10.4.0 and 10.5.0; this is a binary breaking change and consumers need to update to consume the updated property.... (truncated)
10.5.0
HTTP Logging Middleware APIs in
Microsoft.AspNetCore.Diagnostics.Middlewareare now stable. This release also transfersMicrosoft.Extensions.VectorData.AbstractionsandMicrosoft.Extensions.VectorData.ConformanceTestsfrom the Semantic Kernel repository into dotnet/extensions, jumping from 10.1.0 to 10.5.0 for consistent versioning. The release also delivers fixes across the AI libraries, AI Evaluation, and Service Discovery.Breaking Changes
VectorStoreVectorAttributeconstructor parameter #7460Dimensionsparameter was renamed todimensions(lowercase). This is a source-breaking change only — binary compatibility is preserved.new VectorStoreVectorAttribute(Dimensions: 1536), update it tonew VectorStoreVectorAttribute(dimensions: 1536).Experimental API Changes
Now Stable
EXTEXP0013):AddHttpLogEnricher<T>,IHttpLogEnricher, andRequestHeadersLogEnricherOptions.HeadersDataClasses#7380What's Changed
AI
Vector Data
AI Evaluation
Description has been truncated
Dependabo...
Description has been truncated