chore(deps): update aspire to 13.4.6

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Aspire.AppHost.Sdk	msbuild-sdk	patch	13.4.5 → 13.4.6
Aspire.Hosting.AppHost	nuget	patch	13.4.5 → 13.4.6
Aspire.Hosting.PostgreSQL	nuget	patch	13.4.5 → 13.4.6
Aspire.Hosting.RabbitMQ	nuget	patch	13.4.5 → 13.4.6
Aspire.Hosting.Redis	nuget	patch	13.4.5 → 13.4.6
Aspire.Hosting.Testing	nuget	patch	13.4.5 → 13.4.6
Aspire.Npgsql.EntityFrameworkCore.PostgreSQL	nuget	patch	13.4.5 → 13.4.6
Aspire.StackExchange.Redis	nuget	patch	13.4.5 → 13.4.6
Aspire.StackExchange.Redis.OutputCaching	nuget	patch	13.4.5 → 13.4.6

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[claude]

This is a Renovate-generated patch bump of all Aspire packages from 13.4.5 to 13.4.6. The diff is a mechanical version string replacement across 7 project files and Directory.Packages.props — no logic changes, no API surface changes.

A few observations:

Version consistency — The bump is internally consistent: every Aspire reference (SDK, hosting, client, and template packages) moves in lockstep to 13.4.6. There are no mixed versions left behind, which is the main risk with multi-package bumps like this.

Template files included — The TUnit.Templates/content/ tree is updated as well, which is correct. Template projects that shipped pinned to 13.4.5 would have created new projects immediately out of date.

Directory.Packages.props vs. inline PackageReference — Some packages (e.g., Aspire.Hosting.AppHost, Aspire.Hosting.Testing) are centrally managed via Directory.Packages.props, while others (e.g., Aspire.Hosting.PostgreSQL, Aspire.StackExchange.Redis, inline template packages) still carry explicit Version attributes in their .csproj files. This is a pre-existing inconsistency rather than a problem introduced here, but it does mean future bumps require touching multiple files. Worth a one-time follow-up to move all Aspire references into Directory.Packages.props to simplify future updates.

Auto-merge is enabled — Appropriate for a patch dependency update with no behavioral changes. LGTM from a review perspective.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{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.}