Aspire 13.5.3 is now available
The dotnet/aspire repository published v13.5.3 on 2026-08-25. The release notes list changes including: 📊 Dashboard Graph view could crash for Azure Blob resources — Resources such as those created with AddBlobs use icons containing multiple SVG paths, which…; 🌐 DevTunnel public URLs were….
What was released From the source
dotnet/aspire published v13.5.3 on GitHub on 2026-08-25. Items listed in the release notes include:
- 📊 Dashboard Graph view could crash for Azure Blob resources — Resources such as those created with AddBlobs use icons containing multiple SVG paths, which…
- 🌐 DevTunnel public URLs were missing from the Dashboard and MCP snapshots — DevTunnel port resources could report Running and Healthy while showing no public…
- 🚀 Bumped branding to 13.5.3
At a glance · Runtime & Platform
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
- Read the complete release notes for breaking changes and known issues.
- Update the relevant NuGet packages in a branch and run your tests before merging.
- Try new features or previews in a test project first.
- Check the .NET breaking-changes documentation before upgrading major versions.
Sources and further reading
- Release notes for v13.5.3 on GitHub (original source)
Original: “Aspire 13.5.3”, Aspire releases, published 25 Aug 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.