chore(deps): update dependency polly to 8.7.0#6214
Conversation
thomhurst
added
dependencies
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Review: chore(deps): update dependency polly to 8.7.0
Summary
This is a Renovate-bot-generated automated dependency bump of Polly from 8.6.6 to 8.7.0, touching a single line in Directory.Packages.props. It is a minor (semver) release with no breaking changes.
What the PR Does
Updates the centralised NuGet version pin for Polly in Directory.Packages.props. Two projects consume this package:
TUnit.TestProject— usesPolly.CircuitBreaker.CircuitStateas a test argument type to exercise the analyzer against an external enum; the actual Polly resilience pipeline is not exercised at all.TUnit.Analyzers.Tests— references thePollyassembly to provideCircuitStateas aMetadataReferencein Roslyn analyzer test scaffolding.
Polly is not used in any production engine code — TUnit.Engine/Services/DiscoveryCircuitBreaker.cs is a custom, Polly-free implementation that merely borrows the "circuit breaker" naming pattern.
Issues Found
None. This is a minimal, low-risk change.
- The diff is exactly one line:
8.6.6→8.7.0. - Polly
8.7.0is a non-breaking minor release. The highlighted features (caller cancellation token propagation in hedging/timeout, telemetry refactoring) are in strategies that are not used at all in this repo. - The
CircuitStateenum used in test fixtures is part ofPolly.CircuitBreakerand has not changed between these versions. auto-mergeis already enabled with squash strategy, which is appropriate for this class of update.
Suggested Improvements
No code changes are required or recommended. A few observations for awareness:
-
Polly usage is test-only, not production. If the intent is ever to use Polly for resilience logic in the engine (e.g., retry policies around flaky discovery I/O), the existing
DiscoveryCircuitBreakerwould need to be evaluated alongside it. For now, Polly is purely a test fixture dependency and that is fine. -
Version pin scope. The version is pinned only in
Directory.Packages.props(Central Package Management), which is correct — no individual.csprojoverrides the version. This is the right pattern. -
Changelogs worth noting (no action needed): Polly 8.7.0 adds cancellation token propagation in hedging/timeout strategies and refactors telemetry. Neither feature is exercised here, so there is zero functional impact on TUnit.
Overall Assessment
Approve and merge. Routine, fully automated minor dependency update confined to a single version string in the centralised package manifest. No breaking API changes in Polly 8.7.0 affect TUnit's usage. The auto-merge + squash configuration is appropriate and can be left to proceed automatically.
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.
2 participants
This PR contains the following updates:
8.6.6→8.7.0Release Notes
App-vNext/Polly (Polly)
v8.7.0Compare Source
Highlights
What's Changed
New Contributors
Full Changelog: App-vNext/Polly@8.6.6...8.7.0
Configuration
📅 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 this update again.
This PR has been generated by Mend Renovate.