Runtime & Platform

Aspire 13.4.4 is now available

The dotnet/aspire repository published v13.4.4-release on 2026-06-15. The release notes list changes including: 🔌 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…; 🔍 Resources marked with….

What was released From the source

dotnet/aspire published v13.4.4-release on GitHub on 2026-06-15. Items listed in the release notes include:

  • 🔌 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…
  • 🔍 Resources marked with ExcludeFromMcp() were not consistently filtered from CLI MCP tools — Resources with the resource.excludeFromMcp property were not…
  • 📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#18093, @adamratzman)

At a glance · Runtime & Platform

Stable release13.4.4

What was releasedWhy it mattersWho should careUpgrade considerations

Why it matters Analysis

Changes to the .NET runtime, libraries and application frameworks shape performance, compatibility and the features available to every .NET application. Following them helps teams plan upgrades and adopt improvements deliberately.

Who should care Analysis

  • .NET application developers
  • Library and framework authors
  • Teams planning .NET version upgrades

Upgrade considerations Analysis

  1. Read the complete release notes for breaking changes and known issues.
  2. Update the relevant NuGet packages in a branch and run your tests before merging.
  3. Try new features or previews in a test project first.
  4. Check the .NET breaking-changes documentation before upgrading major versions.

Sources and further reading

Original: “Aspire 13.4.4”, Aspire releases, published 15 Jun 2026, retrieved 16 Oct 2026. This article was generated from the official source using our structured templates and passed automated quality checks. Spotted a mistake? See our corrections policy.