chore(deps): update dependency polly to 8.6.5

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polly	nuget	patch	8.6.4 -> 8.6.5

---

Release Notes

App-vNext/Polly (Polly)

v8.6.5

Compare Source

• Extend NuGet package validation by @​martincostello in #​2762
• Suppress S2094 warning by @​martincostello in #​2765
• Refactor cake script by @​martincostello in #​2769
• Pass timeout to TimeoutRejectedException by @​martincostello in #​2827

---

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 this update again.

---

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

---

This PR has been generated by Renovate Bot.

[claude]

Claude Code is working…

I'll analyze this and get back to you.

View job run

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Polly Dependency Update

Review Tasks:

• Examine the changed file (Directory.Packages.props)
• Analyze Polly 8.6.5 release notes for breaking changes
• Check TUnit's usage of Polly for compatibility concerns
• Assess security implications
• Evaluate test coverage needs

Review Summary

✅ Code Quality & Best Practices

• The change follows proper centralized package management using Directory.Packages.props
• Minor patch version update (8.6.4 → 8.6.5) indicates low risk
• Automated dependency updates via Renovate Bot follow good security practices

✅ Compatibility Assessment
TUnit's usage of Polly is minimal and safe:

• Pipeline usage: Uses Polly.Retry.AsyncRetryPolicy for retry logic in test infrastructure (TUnit.Pipeline/Modules/TestNugetPackageModule.cs:34-35)
• Test usage: Uses Polly.CircuitBreaker.CircuitState enum as test arguments to verify external enum handling

✅ Security & Performance

• Patch version updates typically contain security fixes and performance improvements
• The 8.6.5 release includes enhanced timeout handling in TimeoutRejectedException which improves error diagnostics
• No breaking changes identified that would impact TUnit's limited usage

✅ No Test Coverage Issues

• TUnit's usage is primarily for infrastructure retry logic and enum testing
• The existing test coverage for external enum arguments will continue to work
• No functional changes required for the pipeline retry mechanisms

Recommendation

APPROVE: This is a safe dependency update with no compatibility concerns. The changes in Polly 8.6.5 are non-breaking improvements that enhance error reporting and package validation. TUnit's minimal usage of Polly (retry policies and enum testing) will continue to work without modification.

The automated merge can proceed safely.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Polly Dependency Update

Review Tasks:

• Examine the changed file (Directory.Packages.props)
• Analyze Polly 8.6.5 release notes for breaking changes
• Check TUnit's usage of Polly for compatibility concerns
• Assess security implications
• Evaluate test coverage needs

Review Summary

✅ Code Quality & Best Practices

• The change follows proper centralized package management using Directory.Packages.props
• Minor patch version update (8.6.4 → 8.6.5) indicates low risk
• Automated dependency updates via Renovate Bot follow good security practices

✅ Compatibility Assessment
TUnit's usage of Polly is minimal and safe:

• Pipeline usage: Uses Polly.Retry.AsyncRetryPolicy for retry logic in test infrastructure (TUnit.Pipeline/Modules/TestNugetPackageModule.cs:34-35)
• Test usage: Uses Polly.CircuitBreaker.CircuitState enum as test arguments to verify external enum handling

✅ Security & Performance

• Patch version updates typically contain security fixes and performance improvements
• The 8.6.5 release includes enhanced timeout handling in TimeoutRejectedException which improves error diagnostics
• No breaking changes identified that would impact TUnit's limited usage

✅ No Test Coverage Issues

• TUnit's usage is primarily for infrastructure retry logic and enum testing
• The existing test coverage for external enum arguments will continue to work
• No functional changes required for the pipeline retry mechanisms

Recommendation

APPROVE: This is a safe dependency update with no compatibility concerns. The changes in Polly 8.6.5 are non-breaking improvements that enhance error reporting and package validation. TUnit's minimal usage of Polly (retry policies and enum testing) will continue to work without modification.

The automated merge can proceed safely.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Polly Dependency Update

Review Tasks:

• Examine the changed file (Directory.Packages.props)
• Analyze Polly 8.6.5 release notes for breaking changes
• Check TUnit's usage of Polly for compatibility concerns
• Assess security implications
• Evaluate test coverage needs

Review Summary

✅ Code Quality & Best Practices

• The change follows proper centralized package management using Directory.Packages.props
• Minor patch version update (8.6.4 → 8.6.5) indicates low risk
• Automated dependency updates via Renovate Bot follow good security practices

✅ Compatibility Assessment
TUnit's usage of Polly is minimal and safe:

• Pipeline usage: Uses Polly.Retry.AsyncRetryPolicy for retry logic in test infrastructure (TUnit.Pipeline/Modules/TestNugetPackageModule.cs:34-35)
• Test usage: Uses Polly.CircuitBreaker.CircuitState enum as test arguments to verify external enum handling

✅ Security & Performance

• Patch version updates typically contain security fixes and performance improvements
• The 8.6.5 release includes enhanced timeout handling in TimeoutRejectedException which improves error diagnostics
• No breaking changes identified that would impact TUnit's limited usage

✅ No Test Coverage Issues

• TUnit's usage is primarily for infrastructure retry logic and enum testing
• The existing test coverage for external enum arguments will continue to work
• No functional changes required for the pipeline retry mechanisms

Recommendation

APPROVE: This is a safe dependency update with no compatibility concerns. The changes in Polly 8.6.5 are non-breaking improvements that enhance error reporting and package validation. TUnit's minimal usage of Polly (retry policies and enum testing) will continue to work without modification.

The automated merge can proceed safely.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Polly Dependency Update

Review Tasks:

• Examine the changed file (Directory.Packages.props)
• Analyze Polly 8.6.5 release notes for breaking changes
• Check TUnit's usage of Polly for compatibility concerns
• Assess security implications
• Evaluate test coverage needs

Review Summary

✅ Code Quality & Best Practices

• The change follows proper centralized package management using Directory.Packages.props
• Minor patch version update (8.6.4 → 8.6.5) indicates low risk
• Automated dependency updates via Renovate Bot follow good security practices

✅ Compatibility Assessment
TUnit's usage of Polly is minimal and safe:

• Pipeline usage: Uses Polly.Retry.AsyncRetryPolicy for retry logic in test infrastructure (TUnit.Pipeline/Modules/TestNugetPackageModule.cs:34-35)
• Test usage: Uses Polly.CircuitBreaker.CircuitState enum as test arguments to verify external enum handling

✅ Security & Performance

• Patch version updates typically contain security fixes and performance improvements
• The 8.6.5 release includes enhanced timeout handling in TimeoutRejectedException which improves error diagnostics
• No breaking changes identified that would impact TUnit's limited usage

✅ No Test Coverage Issues

• TUnit's usage is primarily for infrastructure retry logic and enum testing
• The existing test coverage for external enum arguments will continue to work
• No functional changes required for the pipeline retry mechanisms

Recommendation

APPROVE: This is a safe dependency update with no compatibility concerns. The changes in Polly 8.6.5 are non-breaking improvements that enhance error reporting and package validation. TUnit's minimal usage of Polly (retry policies and enum testing) will continue to work without modification.

The automated merge can proceed safely.