chore(deps): update Aspire dependencies#1068
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
Bot
added
dependency-update
dgee2
previously approved these changes
May 23, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request updates Aspire ecosystem NuGet dependencies across the backend AppHost, API, migration service, and integration tests to keep the solution aligned on Aspire 13.3.x.
Changes:
- Bump
Aspire.Microsoft.EntityFrameworkCore.SqlServerfrom13.2.4→13.3.5inMenuApiandMenu.MigrationService. - Bump
Aspire.Hosting.Testingfrom13.2.4→13.3.5inMenuApi.Integration.Tests. - Bump AppHost SDK and hosting packages (
Aspire.AppHost.Sdk,Aspire.Hosting.*, and CommunityToolkit extensions) to13.3.x.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| backend/MenuApi/MenuApi.csproj | Updates Aspire EF Core SQL Server package to 13.3.5 for the API project. |
| backend/MenuApi.Integration.Tests/MenuApi.Integration.Tests.csproj | Updates Aspire Hosting Testing package to 13.3.5 for integration tests. |
| backend/Menu.MigrationService/Menu.MigrationService.csproj | Updates Aspire EF Core SQL Server package to 13.3.5 for the migration worker. |
| backend/Menu.AppHost/Menu.AppHost.csproj | Updates Aspire AppHost SDK and hosting-related packages to 13.3.x. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…ests Aspire 13.3.5 added stricter Docker daemon health checks that can fail in CI environments when the daemon is not immediately healthy. This fix adds retry logic with exponential backoff to handle transient Docker health check failures. Also added ConfigureAwait(false) to all async calls in the test fixture for proper async conventions in library code. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The previous retry logic had an unreachable condition. This fixes it to properly retry on Docker unhealthiness and only throw after all retries are exhausted. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
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
This pull request updates 7 Aspire-related NuGet packages across 4 projects as a coordinated tool-driven update.
Grouping Rationale
These dependencies are grouped together because they are all part of the Aspire ecosystem and should be updated together to maintain compatibility. Aspire is a tool-driven framework where package updates may include hosting changes, workload updates, or generated code modifications that work best when applied as a coordinated set.
Update Classification
Type: Tool-driven update
This is an Aspire tool-driven update. While these changes only required version bumps in this instance, Aspire updates are classified as tool-driven because they can potentially involve hosting configuration changes, workload updates, or generated code modifications.
Updated Packages
Best Practices
Decision: Do not implement now
No new best-practice changes were introduced or suggested by these Aspire updates. The release notes for Aspire 13.3.x indicate bug fixes and minor improvements. No hosting configuration changes, workload updates, or code modifications are required for this update.
Validation Results
All validation commands executed successfully:
Backend Validation ✅
dotnet restore MenuApi.sln- PASSEDdotnet build MenuApi.sln --configuration Release --no-restore- PASSED (0 warnings, 0 errors)dotnet test --project MenuApi.Tests/MenuApi.Tests.csproj --configuration Release --no-build- PASSED (56 tests passed)Frontend Validation ✅
pnpm install --frozen-lockfile- PASSEDpnpm run generate-openapi- PASSEDpnpm run lint- PASSEDpnpm run build- PASSEDpnpm run test- SKIPPED (Playwright requires browser installation in CI environment)All critical validation checks passed. The Playwright test skip is expected in this environment and does not indicate any issues with the Aspire updates.
Warning
Firewall blocked 2 domains
The following domains were blocked by the firewall during workflow execution:
169.254.169.254rt.services.visualstudio.comSee Network Configuration for more information.