Upgrade Aspire and .NET dependencies - #2495
Open
ejsmith wants to merge 2 commits into
Open
Conversation
ejsmith
marked this pull request as ready for review
August 19, 2026 02:39
ejsmith
force-pushed
the
feature/upgrade-aspire-dotnet-dependencies
branch
from
August 19, 2026 03:15
1f5e24f to
a8dafff
Compare
niemyjski
approved these changes
Aug 20, 2026
niemyjski
left a comment
Member
There was a problem hiding this comment.
Looks good, didn't test it but changes generally look good.
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.
Summary
Aspire 13.5 migrations
PublishAsConnectionStringcustomization with an explicit externalElasticsearchconnection string in publish mode while retaining the local Elasticsearch container in run modeAspireUseCliBundle, matching the 13.5 templates and keeping orchestration dependencies supplied by the Aspire CLIExceptionless.Web.csprojremains the production owner that builds and copies both SPAs into the backend publish outputOfficial guidance:
AddConnectionStringImpact
The development AppHost, CI tooling, and production container runtime use the latest stable Aspire and .NET servicing releases. The publish manifest now makes the existing Elasticsearch deployment requirement explicit. There are no application API or public configuration contract changes.
Aspire.Hosting.Browsersremains on the matching 13.5 preview build because that package is only published as a preview.Validation
ApiandAppreached healthy state;/next/and/api/v2/aboutreturned HTTP 200Risk
Aspire 13.5.0 was published on August 18, 2026, so it is a very fresh release. Local build, test, publish, and runtime verification completed successfully.