chore(deps): update aspire to 13.3.2#5924
Conversation
There was a problem hiding this comment.
Code Review: Aspire 13.3.1 → 13.3.2 Dependency Update
Overall: LGTM — this is a clean, mechanical patch bump with no concerns.
What was checked
All 9 Aspire packages listed in the PR description are consistently updated from 13.3.1 to 13.3.2 across every file that references them:
| Package | Updated? |
|---|---|
| Aspire.AppHost.Sdk (SDK declarations) | ✅ |
| Aspire.Hosting.AppHost | ✅ |
| Aspire.Hosting.PostgreSQL | ✅ |
| Aspire.Hosting.RabbitMQ | ✅ |
| Aspire.Hosting.Redis | ✅ |
| Aspire.Hosting.Testing | ✅ |
| Aspire.Npgsql.EntityFrameworkCore.PostgreSQL | ✅ |
| Aspire.StackExchange.Redis | ✅ |
| Aspire.StackExchange.Redis.OutputCaching | ✅ |
No package was missed or left at the old version. There are no version mismatches between the SDK declarations and the package references.
Minor observation (no action needed)
The template files under TUnit.Templates/content/TUnit.Aspire.Starter/ pin versions directly rather than using central package management (Directory.Packages.props). This is expected and intentional — templates must be self-contained so they work when extracted in isolation. Just means Renovate needs to update them separately, which it correctly did here.
Safe to merge.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This PR contains the following updates:
13.3.1→13.3.213.3.1→13.3.213.3.1→13.3.213.3.1→13.3.213.3.1→13.3.213.3.1→13.3.213.3.1→13.3.213.3.1→13.3.213.3.1→13.3.2Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate.