chore(deps): update aspire to 13.0.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Aspire.AppHost.Sdk	msbuild-sdk	patch	13.0.0 -> 13.0.1
Aspire.Hosting.AppHost	nuget	patch	13.0.0 -> 13.0.1
Aspire.Hosting.Redis	nuget	patch	13.0.0 -> 13.0.1
Aspire.Hosting.Testing	nuget	patch	13.0.0 -> 13.0.1
Aspire.StackExchange.Redis.OutputCaching	nuget	patch	13.0.0 -> 13.0.1

---

Release Notes

dotnet/aspire (Aspire.AppHost.Sdk)

v13.0.1: Aspire 13.0.1 Release

What's Changed

• Merge internal changes by @​joperezr in #​12896
• [release/13.0] Fix Azure roles resources always redeploying by @​github-actions[bot] in #​12903
• [release/13.0] Remove .py and .js files from being signed (#​13005) by @​eerhardt in #​13032
• [release/13.0] Fix subscription ID not being disabled on Azure provisioning dialog by @​github-actions[bot] in #​12913
• [release/13.0] Default OpenAISettings.EnableSensitiveTelemetryData to TelemetryHelpers.EnableSensitiveDataDefault by @​github-actions[bot] in #​13017
• Bump patch version from 13.0.0 to 13.0.1 by @​Copilot in #​13167
• [release/13.0] EndpointReference evaluation should wait on missing AllocatedEndpoint (#​13074) by @​karolz-ms in #​13076
• [release/13.0] Update to Npgsql 10 by @​github-actions[bot] in #​13166
• [release/13.0] Update dependencies from microsoft/usvc-apiserver by @​danegsta in #​13187

Full Changelog: dotnet/aspire@v13.0.0...v13.0.1

---

Configuration

📅 Schedule: 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 Renovate Bot.

[claude]

Claude finished @thomhurst's task —— View job

---

Dependency Update Review

Todo List

• Analyze changed files and dependency updates
• Review Aspire 13.0.1 release notes for breaking changes
• Check for security implications
• Assess performance considerations
• Evaluate test coverage needs
• Provide final review feedback

Review Summary

This is a low-risk patch update from Aspire 13.0.0 to 13.0.1. Based on my analysis:

✅ Code Quality & Best Practices

• Clean dependency update: All version changes are consistent across template files
• Proper template structure: Changes maintain the existing project structure and dependencies
• No breaking changes: This is a patch release with bug fixes only

✅ Potential Issues Assessment

• No breaking changes identified: The 13.0.1 release contains only bug fixes and minor improvements
• Template consistency: All Aspire packages updated uniformly across templates
• Target framework compatibility: All projects target .NET 10.0 which is compatible

✅ Security Considerations

• Patch release security: Updates include fixes for Azure provisioning and telemetry data handling
• No new attack vectors: Patch updates typically reduce security surface area
• Maintained security practices: No changes to authentication or authorization patterns

✅ Performance Considerations

• Likely improvements: Patch releases often include performance optimizations
• Specific improvements in 13.0.1:
  • Updated to Npgsql 10 (potential database performance improvements)
  • Fixed EndpointReference evaluation timing issues
  • Removed unnecessary file signing overhead

✅ Test Coverage

• Template scope: These are template files, not runtime code
• Existing test coverage: TUnit test framework integration remains unchanged
• Integration testing: Aspire.Hosting.Testing package updated maintains test compatibility

Notable Changes from Release Notes

1. Azure roles deployment fix: Prevents unnecessary redeployments
2. Telemetry improvements: Better handling of sensitive data in OpenAI settings
3. EndpointReference timing fix: Resolves race conditions in endpoint allocation
4. Npgsql update: Database driver improvements

Recommendation

✅ APPROVE - This is a safe patch update that:

• Fixes several bugs without introducing breaking changes
• Improves Azure integration reliability
• Maintains full compatibility with existing TUnit templates
• Follows semantic versioning correctly (patch-level changes only)

The changes are isolated to template files and represent routine dependency maintenance with beneficial bug fixes.