Bump the nuget group with 20 updates by dependabot[bot] · Pull Request #44 · sgbj/surefire

dependabot · 2026-06-17T09:14:19Z

Updated Aspire.Hosting.PostgreSQL from 13.4.2 to 13.4.5.

Release notes

Sourced from Aspire.Hosting.PostgreSQL's releases.

13.4.5 What's New in Aspire 13.4.5

Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry.

🐛 Fixes

🛡️ Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use MessagePackFormatter or LZ4 — all StreamJsonRpc calls use SystemTextJsonFormatter over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the Aspire.Hosting package. (#18204, @mitchdenny)
🎭 playwrightCliVersion values that are not valid SemVer 2.0 now fail fast with a clear diagnostic — Previously an invalid override (range expression, dist-tag like latest, or a v-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. (#18205, @mitchdenny)
🤖 CLI telemetry now detects and reports the calling coding agent — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as copilot-cli. (#18240, @damianedwards)

🏷️ Housekeeping

📄 Refreshed the @microsoft/aspire-cli npm package README to be TypeScript-only — updated examples to the current ts-starter template (apphost.mts / aspire.mjs), added a backing-services snippet showing aspire add for PostgreSQL and Redis, and documented aspire dashboard run as a standalone dashboard option. (#18221, @adamint)

Full Changelog: v13.4.4...v13.4.5

Full commit: 73114e86c64aeb9f3f3c7da8e37df1ae4281b27e

Generated by Generate release notes for a new stable Aspire release · ● 4.4M

13.4.4 What's New in Aspire 13.4.4

Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent ExcludeFromMcp() filtering across all CLI MCP tools.

🐛 Fixes

🔌 DCP requests could fail permanently when the connection dropped mid-request — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. (#18096, @karolz-ms)
🔍 Resources marked with ExcludeFromMcp() were not consistently filtered from CLI MCP tools — Resources with the resource.excludeFromMcp property were not excluded uniformly from all CLI MCP tool results. list_resources, list_console_logs, execute_resource_command, list_structured_logs, list_traces, and list_trace_structured_logs all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. (#18150, @JamesNK)

🏷️ Housekeeping

📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#18093, @adamratzman)

Full Changelog: v13.4.3...v13.4.4

Full commit: ccc566c5ab3285c9beb8f38ede34734bb477c029

13.4.3 What's New in Aspire 13.4.3

Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4.

🐛 Fixes

🔌 Persistent container endpoints had incorrect default behavior — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with isProxied: false or WithEndpointProxySupport(false). Proxyless container endpoints with only a targetPort specified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960, @danegsta)

🏷️ Housekeeping

🛠️ Unblocked WinGet manifest publishing on locked-down 1ES agents and updated manifest tags (#17958)

Full Changelog: microsoft/aspire@v13.4.2...v13.4.3

Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9

Generated by Generate release notes for a new stable Aspire release · ● 4.7M

Commits viewable in compare view.

Updated Aspire.Hosting.Redis from 13.4.2 to 13.4.5.

Release notes

Sourced from Aspire.Hosting.Redis's releases.

13.4.5 What's New in Aspire 13.4.5

Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry.

🐛 Fixes

🛡️ Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use MessagePackFormatter or LZ4 — all StreamJsonRpc calls use SystemTextJsonFormatter over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the Aspire.Hosting package. (#18204, @mitchdenny)
🎭 playwrightCliVersion values that are not valid SemVer 2.0 now fail fast with a clear diagnostic — Previously an invalid override (range expression, dist-tag like latest, or a v-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. (#18205, @mitchdenny)
🤖 CLI telemetry now detects and reports the calling coding agent — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as copilot-cli. (#18240, @damianedwards)

🏷️ Housekeeping

📄 Refreshed the @microsoft/aspire-cli npm package README to be TypeScript-only — updated examples to the current ts-starter template (apphost.mts / aspire.mjs), added a backing-services snippet showing aspire add for PostgreSQL and Redis, and documented aspire dashboard run as a standalone dashboard option. (#18221, @adamint)

Full Changelog: v13.4.4...v13.4.5

Full commit: 73114e86c64aeb9f3f3c7da8e37df1ae4281b27e

Generated by Generate release notes for a new stable Aspire release · ● 4.4M

13.4.4 What's New in Aspire 13.4.4

Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent ExcludeFromMcp() filtering across all CLI MCP tools.

🐛 Fixes

🔌 DCP requests could fail permanently when the connection dropped mid-request — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. (#18096, @karolz-ms)
🔍 Resources marked with ExcludeFromMcp() were not consistently filtered from CLI MCP tools — Resources with the resource.excludeFromMcp property were not excluded uniformly from all CLI MCP tool results. list_resources, list_console_logs, execute_resource_command, list_structured_logs, list_traces, and list_trace_structured_logs all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. (#18150, @JamesNK)

🏷️ Housekeeping

📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#18093, @adamratzman)

Full Changelog: v13.4.3...v13.4.4

Full commit: ccc566c5ab3285c9beb8f38ede34734bb477c029

13.4.3 What's New in Aspire 13.4.3

Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4.

🐛 Fixes

🔌 Persistent container endpoints had incorrect default behavior — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with isProxied: false or WithEndpointProxySupport(false). Proxyless container endpoints with only a targetPort specified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960, @danegsta)

🏷️ Housekeeping

🛠️ Unblocked WinGet manifest publishing on locked-down 1ES agents and updated manifest tags (#17958)

Full Changelog: microsoft/aspire@v13.4.2...v13.4.3

Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9

Generated by Generate release notes for a new stable Aspire release · ● 4.7M

Commits viewable in compare view.

Updated Aspire.Hosting.SqlServer from 13.4.2 to 13.4.5.

Release notes

Sourced from Aspire.Hosting.SqlServer's releases.

13.4.5 What's New in Aspire 13.4.5

Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry.

🐛 Fixes

🛡️ Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use MessagePackFormatter or LZ4 — all StreamJsonRpc calls use SystemTextJsonFormatter over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the Aspire.Hosting package. (#18204, @mitchdenny)
🎭 playwrightCliVersion values that are not valid SemVer 2.0 now fail fast with a clear diagnostic — Previously an invalid override (range expression, dist-tag like latest, or a v-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. (#18205, @mitchdenny)
🤖 CLI telemetry now detects and reports the calling coding agent — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as copilot-cli. (#18240, @damianedwards)

🏷️ Housekeeping

📄 Refreshed the @microsoft/aspire-cli npm package README to be TypeScript-only — updated examples to the current ts-starter template (apphost.mts / aspire.mjs), added a backing-services snippet showing aspire add for PostgreSQL and Redis, and documented aspire dashboard run as a standalone dashboard option. (#18221, @adamint)

Full Changelog: v13.4.4...v13.4.5

Full commit: 73114e86c64aeb9f3f3c7da8e37df1ae4281b27e

Generated by Generate release notes for a new stable Aspire release · ● 4.4M

13.4.4 What's New in Aspire 13.4.4

Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent ExcludeFromMcp() filtering across all CLI MCP tools.

🐛 Fixes

🔌 DCP requests could fail permanently when the connection dropped mid-request — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. (#18096, @karolz-ms)
🔍 Resources marked with ExcludeFromMcp() were not consistently filtered from CLI MCP tools — Resources with the resource.excludeFromMcp property were not excluded uniformly from all CLI MCP tool results. list_resources, list_console_logs, execute_resource_command, list_structured_logs, list_traces, and list_trace_structured_logs all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. (#18150, @JamesNK)

🏷️ Housekeeping

📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#18093, @adamratzman)

Full Changelog: v13.4.3...v13.4.4

Full commit: ccc566c5ab3285c9beb8f38ede34734bb477c029

13.4.3 What's New in Aspire 13.4.3

Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4.

🐛 Fixes

🔌 Persistent container endpoints had incorrect default behavior — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with isProxied: false or WithEndpointProxySupport(false). Proxyless container endpoints with only a targetPort specified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960, @danegsta)

🏷️ Housekeeping

🛠️ Unblocked WinGet manifest publishing on locked-down 1ES agents and updated manifest tags (#17958)

Full Changelog: microsoft/aspire@v13.4.2...v13.4.3

Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9

Generated by Generate release notes for a new stable Aspire release · ● 4.7M

Commits viewable in compare view.

Updated Aspire.Microsoft.Data.SqlClient from 13.4.2 to 13.4.5.

Release notes

Sourced from Aspire.Microsoft.Data.SqlClient's releases.

13.4.5 What's New in Aspire 13.4.5

Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry.

🐛 Fixes

🛡️ Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use MessagePackFormatter or LZ4 — all StreamJsonRpc calls use SystemTextJsonFormatter over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the Aspire.Hosting package. (#18204, @mitchdenny)
🎭 playwrightCliVersion values that are not valid SemVer 2.0 now fail fast with a clear diagnostic — Previously an invalid override (range expression, dist-tag like latest, or a v-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. (#18205, @mitchdenny)
🤖 CLI telemetry now detects and reports the calling coding agent — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as copilot-cli. (#18240, @damianedwards)

🏷️ Housekeeping

📄 Refreshed the @microsoft/aspire-cli npm package README to be TypeScript-only — updated examples to the current ts-starter template (apphost.mts / aspire.mjs), added a backing-services snippet showing aspire add for PostgreSQL and Redis, and documented aspire dashboard run as a standalone dashboard option. (#18221, @adamint)

Full Changelog: v13.4.4...v13.4.5

Full commit: 73114e86c64aeb9f3f3c7da8e37df1ae4281b27e

Generated by Generate release notes for a new stable Aspire release · ● 4.4M

13.4.4 What's New in Aspire 13.4.4

Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent ExcludeFromMcp() filtering across all CLI MCP tools.

🐛 Fixes

🔌 DCP requests could fail permanently when the connection dropped mid-request — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. (#18096, @karolz-ms)
🔍 Resources marked with ExcludeFromMcp() were not consistently filtered from CLI MCP tools — Resources with the resource.excludeFromMcp property were not excluded uniformly from all CLI MCP tool results. list_resources, list_console_logs, execute_resource_command, list_structured_logs, list_traces, and list_trace_structured_logs all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. (#18150, @JamesNK)

🏷️ Housekeeping

📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#18093, @adamratzman)

Full Changelog: v13.4.3...v13.4.4

Full commit: ccc566c5ab3285c9beb8f38ede34734bb477c029

13.4.3 What's New in Aspire 13.4.3

Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4.

🐛 Fixes

🔌 Persistent container endpoints had incorrect default behavior — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with isProxied: false or WithEndpointProxySupport(false). Proxyless container endpoints with only a targetPort specified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960, @danegsta)

🏷️ Housekeeping

🛠️ Unblocked WinGet manifest publishing on locked-down 1ES agents and updated manifest tags (#17958)

Full Changelog: microsoft/aspire@v13.4.2...v13.4.3

Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9

Generated by Generate release notes for a new stable Aspire release · ● 4.7M

Commits viewable in compare view.

Updated Aspire.Npgsql from 13.4.2 to 13.4.5.

Release notes

Sourced from Aspire.Npgsql's releases.

13.4.5 What's New in Aspire 13.4.5

Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry.

🐛 Fixes

🛡️ Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use MessagePackFormatter or LZ4 — all StreamJsonRpc calls use SystemTextJsonFormatter over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the Aspire.Hosting package. (#18204, @mitchdenny)
🎭 playwrightCliVersion values that are not valid SemVer 2.0 now fail fast with a clear diagnostic — Previously an invalid override (range expression, dist-tag like latest, or a v-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. (#18205, @mitchdenny)
🤖 CLI telemetry now detects and reports the calling coding agent — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as copilot-cli. (#18240, @damianedwards)

🏷️ Housekeeping

📄 Refreshed the @microsoft/aspire-cli npm package README to be TypeScript-only — updated examples to the current ts-starter template (apphost.mts / aspire.mjs), added a backing-services snippet showing aspire add for PostgreSQL and Redis, and documented aspire dashboard run as a standalone dashboard option. (#18221, @adamint)

Full Changelog: v13.4.4...v13.4.5

Full commit: 73114e86c64aeb9f3f3c7da8e37df1ae4281b27e

Generated by Generate release notes for a new stable Aspire release · ● 4.4M

13.4.4 What's New in Aspire 13.4.4

Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent ExcludeFromMcp() filtering across all CLI MCP tools.

🐛 Fixes

🔌 DCP requests could fail permanently when the connection dropped mid-request — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. (#18096, @karolz-ms)
🔍 Resources marked with ExcludeFromMcp() were not consistently filtered from CLI MCP tools — Resources with the resource.excludeFromMcp property were not excluded uniformly from all CLI MCP tool results. list_resources, list_console_logs, execute_resource_command, list_structured_logs, list_traces, and list_trace_structured_logs all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. (#18150, @JamesNK)

🏷️ Housekeeping

📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#18093, @adamratzman)

Full Changelog: v13.4.3...v13.4.4

Full commit: ccc566c5ab3285c9beb8f38ede34734bb477c029

13.4.3 What's New in Aspire 13.4.3

Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4.

🐛 Fixes

🔌 Persistent container endpoints had incorrect default behavior — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with isProxied: false or WithEndpointProxySupport(false). Proxyless container endpoints with only a targetPort specified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960, @danegsta)

🏷️ Housekeeping

🛠️ Unblocked WinGet manifest publishing on locked-down 1ES agents and updated manifest tags (#17958)

Full Changelog: microsoft/aspire@v13.4.2...v13.4.3

Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9

Generated by Generate release notes for a new stable Aspire release · ● 4.7M

Commits viewable in compare view.

Updated Aspire.StackExchange.Redis from 13.4.2 to 13.4.5.

Release notes

Sourced from Aspire.StackExchange.Redis's releases.

13.4.5 What's New in Aspire 13.4.5

Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry.

🐛 Fixes

🛡️ Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use MessagePackFormatter or LZ4 — all StreamJsonRpc calls use SystemTextJsonFormatter over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the Aspire.Hosting package. (#18204, @mitchdenny)
🎭 playwrightCliVersion values that are not valid SemVer 2.0 now fail fast with a clear diagnostic — Previously an invalid override (range expression, dist-tag like latest, or a v-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. (#18205, @mitchdenny)
🤖 CLI telemetry now detects and reports the calling coding agent — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as copilot-cli. (#18240, @damianedwards)

🏷️ Housekeeping

📄 Refreshed the @microsoft/aspire-cli npm package README to be TypeScript-only — updated examples to the current ts-starter template (apphost.mts / aspire.mjs), added a backing-services snippet showing aspire add for PostgreSQL and Redis, and documented aspire dashboard run as a standalone dashboard option. (#18221, @adamint)

Full Changelog: v13.4.4...v13.4.5

Full commit: 73114e86c64aeb9f3f3c7da8e37df1ae4281b27e

Generated by Generate release notes for a new stable Aspire release · ● 4.4M

13.4.4 What's New in Aspire 13.4.4

Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent ExcludeFromMcp() filtering across all CLI MCP tools.

🐛 Fixes

🔌 DCP requests could fail permanently when the connection dropped mid-request — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. (#18096, @karolz-ms)
🔍 Resources marked with ExcludeFromMcp() were not consistently filtered from CLI MCP tools — Resources with the resource.excludeFromMcp property were not excluded uniformly from all CLI MCP tool results. list_resources, list_console_logs, execute_resource_command, list_structured_logs, list_traces, and list_trace_structured_logs all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. (#18150, @JamesNK)

🏷️ Housekeeping

📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#18093, @adamratzman)

Full Changelog: v13.4.3...v13.4.4

Full commit: ccc566c5ab3285c9beb8f38ede34734bb477c029

13.4.3 What's New in Aspire 13.4.3

Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4.

🐛 Fixes

🔌 Persistent container endpoints had incorrect default behavior — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with isProxied: false or WithEndpointProxySupport(false). Proxyless container endpoints with only a targetPort specified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960, @danegsta)

🏷️ Housekeeping

🛠️ Unblocked WinGet manifest publishing on locked-down 1ES agents and updated manifest tags (#17958)

Full Changelog: microsoft/aspire@v13.4.2...v13.4.3

Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9

Generated by Generate release notes for a new stable Aspire release · ● 4.7M

Commits viewable in compare view.

Updated Microsoft.AspNetCore.TestHost from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.AspNetCore.TestHost's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Data.Sqlite from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.Data.Sqlite's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.DependencyInjection from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.Extensions.DependencyInjection's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Diagnostics from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.Extensions.Diagnostics's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Diagnostics.HealthChecks from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.Extensions.Diagnostics.HealthChecks's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.FileProviders.Embedded from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.Extensions.FileProviders.Embedded's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Hosting from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.Extensions.Hosting's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Http.Resilience from 10.6.0 to 10.7.0.

Release notes

Sourced from Microsoft.Extensions.Http.Resilience's releases.

10.7.0

v10.7.0 graduates the Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package to stable. The package registers a Kubernetes-aware ResourceQuotaProvider that reads the pod's CPU and memory requests and limits and exposes them to Microsoft.Extensions.Diagnostics.ResourceMonitoring as baseline and maximum quotas, which then feed the request and limit dimensions of the published resource utilization metrics. The companion ResourceQuota and ResourceQuotaProvider types in Microsoft.Extensions.Diagnostics.ResourceMonitoring graduate 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.OpenAI moves to OpenAI 2.11.0 and fixes a deserialization bug in ToolJson.AdditionalProperties so that JSON Schema additionalProperties values shaped as sub-schema objects (for example {"type":"string"}) are preserved instead of throwing during deserialization. HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt graduate to stable since both values are consistently available across hosted-file providers, while Purpose and Scope remain experimental as provider-shaped vocabulary. FunctionInvokingChatClient drops a backward-compat path that auto-marked ToolApprovalResponseContent entries with InformationalOnly: true; consumers that need to continue accepting sessions serialized before #7468 can use the sample ApprovalHistoryNormalizingChatClient middleware added in the test project.

Experimental API Changes

Now Stable

Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package is now stable #7253
Resource Monitoring ResourceQuota and ResourceQuotaProvider APIs are now stable (previously EXTEXP0008) #7253
HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt are now stable (previously MEAI001) #7513

What's Changed

AI

Graduate HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt #7513 by @jozkee (co-authored by @Copilot)
Remove backward-compat InformationalOnly case from FICC; suggest middleware workaround #7538 by @jozkee (co-authored by @Copilot)
Upgrade OpenAI package from 2.10.0 to 2.11.0 #7544 by @jozkee (co-authored by @Copilot)
Fix ToolJson.AdditionalProperties to accept sub-schema objects #7546 by @jozkee (co-authored by @Copilot)

Diagnostics, Health Checks, and Resource Monitoring

Move Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes to stable #7253 by @amadeuszl (co-authored by @Copilot)

Repository Infrastructure Updates

[main] Update dependencies from dotnet/arcade #7521
Bump dotnet-reportgenerator-globaltool from 5.5.9 to 5.5.10 #7522
Bump dotnet-coverage from 18.6.2 to 18.7.0 #7530
Bump PowerShell from 7.6.1 to 7.6.2 #7531
Bump qs from 6.15.1 to 6.15.2 in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7532
[main] Update dependencies from dotnet/arcade #7534
Bump tmp from 0.2.5 to 0.2.6 in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7537

Acknowledgements

@ericstj submitted issue #7509 (resolved by #7544)
@scottt732 submitted issue #7540 (resolved by #7546)
@DeagleGross @wtgodbe @dariusclay @evgenyfedorov2 @peterwald @PranavSenthilnathan @shyamnamboodiripad @stephentoub @tarekgh reviewed pull requests

Full Changelog: dotnet/extensions@v10.6.0...v10.7.0

Commits viewable in compare view.

Updated Microsoft.Extensions.Logging from 10.0.8 to 10.0.9.

Release notes

Sourced from Microsoft.Extensions.Logging's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.ServiceDiscovery from 10.6.0 to 10.7.0.

Release notes

Sourced from Microsoft.Extensions.ServiceDiscovery's releases.

10.7.0

v10.7.0 graduates the Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package to stable. The package registers a Kubernetes-aware ResourceQuotaProvider that reads the pod's CPU and memory requests and limits and exposes them to Microsoft.Extensions.Diagnostics.ResourceMonitoring as baseline and maximum quotas, which then feed the request and limit dimensions of the published resource utilization metrics. The companion ResourceQuota and ResourceQuotaProvider types in Microsoft.Extensions.Diagnostics.ResourceMonitoring graduate 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.OpenAI moves to OpenAI 2.11.0 and fixes a deserialization bug in ToolJson.AdditionalProperties so that JSON Schema additionalProperties values shaped as sub-schema objects (for example {"type":"string"}) are preserved instead of throwing during deserialization. HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt graduate to stable since both values are consistently available across hosted-file providers, while Purpose and Scope remain experimental as provider-shaped vocabulary. FunctionInvokingChatClient drops a backward-compat path that auto-marked ToolApprovalResponseContent entries with InformationalOnly: true; consumers that need to continue accepting sessions serialized before #7468 can use the sample ApprovalHistoryNormalizingChatClient middleware added in the test project.

Experimental API Changes

Now Stable

Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package is now stable #7253
Resource Monitoring ResourceQuota and ResourceQuotaProvider APIs are now stable (previously EXTEXP0008) #7253
HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt are now stable (previously MEAI001) #7513

What's Changed

AI

Graduate HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt #7513 by @jozkee (co-authored by @Copilot)
Remove backward-compat InformationalOnly case from FICC; suggest middleware workaround #7538 by @jozkee (co-authored by @Copilot)
Upgrade OpenAI package from 2.10.0 to 2.11.0 #7544 by @jozkee (co-authored by @Copilot)
Fix ToolJson.AdditionalProperties to accept sub-schema objects #7546 by @jozkee (co-authored by @Copilot)

Diagnostics, Health Checks, and Resource Monitoring

Move Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes to stable #7253 by @amadeuszl (co-authored by @Copilot)

Repository Infrastructure Updates

[main] Update dependencies from dotnet/arcade #7521
Bump dotnet-reportgenerator-globaltool from 5.5.9 to 5.5.10 #7522
Bump dotnet-coverage from 18.6.2 to 18.7.0 #7530
Bump PowerShell from 7.6.1 to 7.6.2 #7531
Bump qs from 6.15.1 to 6.15.2 in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7532
[main] Update dependencies from dotnet/arcade #7534
Bump tmp from 0.2.5 to 0.2.6 in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7537

Acknowledgements

@ericstj submitted issue #7509 (resolved by #7544)
@scottt732 submitted issue #7540 (resolved by #7546)
@DeagleGross @wtgodbe @dariusclay @evgenyfedorov2 @peterwald @PranavSenthilnathan @shyamnamboodiripad @stephentoub @tarekgh reviewed pull requests

Full Changelog: dotnet/extensions@v10.6.0...v10.7.0

Commits viewable in compare view.

Updated Microsoft.Extensions.TimeProvider.Testing from 10.6.0 to 10.7.0.

Release notes

Sourced from Microsoft.Extensions.TimeProvider.Testing's releases.

10.7.0

v10.7.0 graduates the Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package to stable. The package registers a Kubernetes-aware ResourceQuotaProvider that reads the pod's CPU and memory requests and limits and exposes them to Microsoft.Extensions.Diagnostics.ResourceMonitoring as baseline and maximum quotas, which then feed the request and limit dimensions of the published resource utilization metrics. The companion ResourceQuota and ResourceQuotaProvider types in Microsoft.Extensions.Diagnostics.ResourceMonitoring graduate 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.OpenAI moves to OpenAI 2.11.0 and fixes a deserialization bug in ToolJson.AdditionalProperties so that JSON Schema additionalProperties values shaped as sub-schema objects (for example {"type":"string"}) are preserved instead of throwing during deserialization. HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt graduate to stable since both values are consistently available across hosted-file providers, while Purpose and Scope remain experimental as provider-shaped vocabulary. FunctionInvokingChatClient drops a backward-compat path that auto-marked ToolApprovalResponseContent entries with InformationalOnly: true; consumers that need to continue accepting sessions serialized before #7468 can use the sample ApprovalHistoryNormalizingChatClient middleware added in the test project.

Experimental API Changes

Now Stable

Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package is now stable #7253
Resource Monitoring ResourceQuota and ResourceQuotaProvider APIs are now stable (previously EXTEXP0008) #7253
HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt are now stable (previously MEAI001) #7513

What's Changed

AI

Graduate HostedFileContent.SizeInBytes and HostedFileContent.CreatedAt #7513 by @jozkee (co-authored by @Copilot)
Remove backward-compat InformationalOnly case from FICC; suggest middleware workaround #7538 by @jozkee (co-authored by @Copilot)
Upgrade OpenAI package from 2.10.0 to 2.11.0 #7544 by @jozkee (co-authored by @Copilot)
Fix ToolJson.AdditionalProperties to accept sub-schema objects #7546 by @jozkee (co-authored by @Copilot)

Diagnostics, Health Checks, and Resource Monitoring

Move Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes to stable #7253 by @amadeuszl (co-authored by @Copilot)

Repository Infrastructure Updates

[main] Update dependencies from dotnet/arcade #7521
Bump dotnet-reportgenerator-globaltool from 5.5.9 to 5.5.10 #7522
Bump dotnet-coverage from 18.6.2 to 18.7.0 #7530
Bump PowerShell from 7.6.1 to 7.6.2 #7531
Bump qs from 6.15.1 to 6.15.2 in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7532
[main] Update dependencies from dotnet/arcade #7534
Bump tmp from 0.2.5 to 0.2.6 in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7537

Acknowledgements

@ericstj submitted issue #7509 (resolved by #7544)
@scottt732 submitted issue #7540 (resolved by #7546)
@DeagleGross @wtgodbe @dariusclay @evgenyfedorov2 @peterwald @PranavSenthilnathan @shyamnamboodiripad @stephentoub @tarekgh reviewed pull requests

Full Changelog: dotnet/extensions@v10.6.0...v10.7.0

Commits viewable in compare view.

Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.15.3 to 1.16.0.

Release notes

Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.

1.16.0

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

The following changes are from the previous release 1.16.0-rc.1.

NuGet: OpenTelemetry v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Zipkin v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Extensions.Hosting v1.16.0

No notable changes.

... (truncated)

1.16.0-rc.1

The following changes are from the previous release 1.15.3.

NuGet: OpenTelemetry v1.16.0-rc.1
- Stop validating View-provided metric stream Name against the instrument
  name syntax, per
  spec clarification.
  (#7300)
- Fix incorrect validation of OTEL_BSP_* and OTEL_BLRP_* environment
  variables.
  (#7187)
- Fix observable instrument callbacks running once per reader instead of
  once per collection cycle.
  (#7188)
- Added exception safety for user-supplied ExemplarReservoir implementations.
  Exceptions thrown from Offer are now caught and logged rather than propagating
  out of Counter.Add/Histogram.Record.
  (#7277)
- Update OpenTelemetrySdkEventSource to support the W3C randomness flag.
  (#7301)
- Added ObservedTimestamp property to LogRecord.
  (#6979)
- Breaking Change Explicit histogram boundaries no longer allow more than
  10 million values.
  (#7165)
- Fixed a circular reference which could cause a LoggerProvider to fail to
  resolve when one of its dependencies depends on ILogger or ILoggerFactory.
  As part of this fix the LoggerProvider resolved from dependency injection
  is now created lazily when the first logger is created rather than when
  ILoggerProvider or ILoggerFactory is resolved. A consequence is that any
  invalid configuration now surfaces when the first log record is written instead
  of when the logging services are resolved.
  (#7308)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.16.0-rc.1
- Experimental (pre-release builds only):
  Add support for using environment variables as context propagation carriers.
  (#7174)
- Fix BaggagePropagator to correctly follow Key and Value Encoding rules as per
  ... (truncated)

1.16.0-beta.1

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

NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.16.0-beta.1
- Fixed scrape response cache freshness using monotonic time so it is not
  affected by NTP system clock adjustments.
  (#7253)
- Breaking Change Removed DisableTimestamp property from
  PrometheusAspNetCoreOptions.
  (#7176)
- Fixed the serialization of NaN, PositiveInfinity, and NegativeInfinity
  values in Prometheus metrics to be compliant with the specification.
  (#7179)
- Fixed loss of precision when serializing double and float values in
  Prometheus metrics to be compliant with the specification by using 17
  significant digits to represent such values.
  (#7179)
- Fix non-ASCII characters in metric names and unit strings not being sanitized
  correctly during Prometheus serialization.
  (#7184)
- Fix case where reader tracking could be reset while readers were still active.
  (#7190)
- Improve Accept header handling for format negotiation so OpenMetrics is
  selected correctly by considering whitespace and q weights.
  (#7208)
- Emit OpenMetrics exemplars for counters and histogram buckets.
  (#7222)
- Fix incorrect handling of untyped metrics when using OpenMetrics format.
  (#7219)
- Fix Prometheus/OpenMetrics serialization to emit metric and label names
  containing _ instead of dropping them and prefixing leading digits.
  Invalid characters are replaced with _ instead of being dropped.
  (#7209)
- Add escaping=underscores to the Accept header handling for content
  negotiation so OpenMetrics are handled correctly.
  (#7209)
- Omit histogram _sum and _count in OpenMetrics when negative bucket
  thresholds are present.
  (#7221)
  ... (truncated)

Commits viewable in compare view.

Updated OpenTelemetry.Extensions.Hosting from 1.15.3 to 1.16.0.

Release notes

Sourced from OpenTelemetry.Extensions.Hosting's releases.

1.16.0

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

The following changes are from the previous release 1.16.0-rc.1.

NuGet: OpenTelemetry v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.16.0

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Zipkin v1.16.0

No notable changes.

See [CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet/b...

Description has been truncated

Dependabot will resolve any conflicts with this PR ...

Description has been truncated

Bumps Aspire.Hosting.PostgreSQL from 13.4.2 to 13.4.5 Bumps Aspire.Hosting.Redis from 13.4.2 to 13.4.5 Bumps Aspire.Hosting.SqlServer from 13.4.2 to 13.4.5 Bumps Aspire.Microsoft.Data.SqlClient from 13.4.2 to 13.4.5 Bumps Aspire.Npgsql from 13.4.2 to 13.4.5 Bumps Aspire.StackExchange.Redis from 13.4.2 to 13.4.5 Bumps Microsoft.AspNetCore.TestHost from 10.0.8 to 10.0.9 Bumps Microsoft.Data.Sqlite from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.DependencyInjection from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Diagnostics from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Diagnostics.HealthChecks from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.FileProviders.Embedded from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Hosting from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Http.Resilience from 10.6.0 to 10.7.0 Bumps Microsoft.Extensions.Logging from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.ServiceDiscovery from 10.6.0 to 10.7.0 Bumps Microsoft.Extensions.TimeProvider.Testing from 10.6.0 to 10.7.0 Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.15.3 to 1.16.0 Bumps OpenTelemetry.Extensions.Hosting from 1.15.3 to 1.16.0 Bumps StackExchange.Redis from 2.13.17 to 3.0.0 --- updated-dependencies: - dependency-name: Aspire.Hosting.PostgreSQL dependency-version: 13.4.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Aspire.Hosting.Redis dependency-version: 13.4.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Aspire.Hosting.SqlServer dependency-version: 13.4.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Aspire.Microsoft.Data.SqlClient dependency-version: 13.4.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Aspire.Npgsql dependency-version: 13.4.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Aspire.StackExchange.Redis dependency-version: 13.4.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.AspNetCore.TestHost dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Data.Sqlite dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.DependencyInjection dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Diagnostics dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Diagnostics.HealthChecks dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.FileProviders.Embedded dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Hosting dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.7.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Microsoft.Extensions.Logging dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.ServiceDiscovery dependency-version: 10.7.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Microsoft.Extensions.TimeProvider.Testing dependency-version: 10.7.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.16.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.16.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: StackExchange.Redis dependency-version: 3.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2026-06-24T09:14:43Z

Superseded by #47.

dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Jun 17, 2026

dependabot Bot mentioned this pull request Jun 17, 2026

Bump the nuget group with 17 updates #41

Closed

dependabot Bot closed this Jun 24, 2026

dependabot Bot deleted the dependabot/nuget/nuget-607a1536a0 branch June 24, 2026 09:14

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump the nuget group with 20 updates#44

Bump the nuget group with 20 updates#44
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/nuget-607a1536a0

dependabot Bot commented on behalf of github Jun 17, 2026 •

edited

Loading

Uh oh!

dependabot Bot commented on behalf of github Jun 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Jun 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

13.4.5

What's New in Aspire 13.4.5

🐛 Fixes

🏷️ Housekeeping

13.4.4

What's New in Aspire 13.4.4

🐛 Fixes

🏷️ Housekeeping

13.4.3

What's New in Aspire 13.4.3

🐛 Fixes

🏷️ Housekeeping

13.4.5

What's New in Aspire 13.4.5

🐛 Fixes

🏷️ Housekeeping

13.4.4

What's New in Aspire 13.4.4

🐛 Fixes

🏷️ Housekeeping

13.4.3

What's New in Aspire 13.4.3

🐛 Fixes

🏷️ Housekeeping

13.4.5

What's New in Aspire 13.4.5

🐛 Fixes

🏷️ Housekeeping

13.4.4

What's New in Aspire 13.4.4

🐛 Fixes

🏷️ Housekeeping

13.4.3

What's New in Aspire 13.4.3

🐛 Fixes

🏷️ Housekeeping

13.4.5

What's New in Aspire 13.4.5

🐛 Fixes

🏷️ Housekeeping

13.4.4

What's New in Aspire 13.4.4

🐛 Fixes

🏷️ Housekeeping

13.4.3

What's New in Aspire 13.4.3

🐛 Fixes

🏷️ Housekeeping

13.4.5

What's New in Aspire 13.4.5

🐛 Fixes

🏷️ Housekeeping

13.4.4

What's New in Aspire 13.4.4

🐛 Fixes

🏷️ Housekeeping

13.4.3

What's New in Aspire 13.4.3

🐛 Fixes

🏷️ Housekeeping

13.4.5

What's New in Aspire 13.4.5

🐛 Fixes

🏷️ Housekeeping

13.4.4

What's New in Aspire 13.4.4

🐛 Fixes

🏷️ Housekeeping

13.4.3

What's New in Aspire 13.4.3

🐛 Fixes

🏷️ Housekeeping

10.7.0

Experimental API Changes

Now Stable

What's Changed

AI

dependabot Bot commented on behalf of github Jun 17, 2026 •

edited

Loading