chore(deps): update _tunitpolyfillversion to 10.8.0 by thomhurst · Pull Request #6167 · thomhurst/TUnit (original) (raw)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This is a clean, minimal automated dependency bump — exactly one line changed, in the right place.

What's Done Well

• Single source of truth preserved. The version is updated in _TUnitPolyfillVersion, which feeds both the non-CPM and CPM PackageReference groups in TUnit.Core.targets. No risk of version skew.
• Compile-time only package. Polyfill is PrivateAssets=all / IncludeAssets=compile;analyzers — a bad bump surfaces as a compile error, not a runtime regression, keeping blast radius minimal.
• Scoped impact. The _TUnitNeedsPolyfill condition means this only affects consumers on netstandard2.0, netstandard2.1, or .NETFramework TFMs. Modern net8.0/net9.0/net10.0 consumers are unaffected.

Minor Note

The Renovate-generated compare link in the PR description appears to have no changelog entries. Since Polyfill is source-only, any issue would be a compile failure caught in CI — so this is acceptable for auto-merge.

Verdict

No issues. This is a low-risk, well-structured automated bump. Auto-merge is appropriate here.