chore(deps): update dependency polyfill to 8.8.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	patch	8.8.0 -> 8.8.1

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v8.8.1

Compare Source

---

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 finished @thomhurst's task —— View job

---

PR Review: Polyfill Dependency Update

I've reviewed this dependency update PR and analyzed the impact across all requested areas.

Todo List:

• Read and analyze the changed file
• Understand the Polyfill package role in TUnit
• Review potential impacts and concerns
• Provide comprehensive feedback

---

🔍 Review Summary

This is a low-risk patch update from Polyfill 8.8.0 → 8.8.1. The change is minimal and safe to merge.

📋 Detailed Analysis

Code Quality & Best Practices ✅

• Change: Single line update in TUnit.Core.targets:11 (8.8.0 → 8.8.1)
• Pattern: Follows TUnit's established approach for dependency version management
• Implementation: Clean, consistent with existing MSBuild property patterns
• Architecture: Properly isolated in .targets file, affecting only necessary target frameworks

Potential Bugs/Issues ✅ None Identified

• Patch version update (8.8.0 → 8.8.1) indicates bug fixes only
• No breaking changes expected per semantic versioning
• TUnit's usage is minimal and well-contained (see TUnit.Engine/PolyfillExtensions.cs:5-10)

Performance Considerations ✅ Positive/Neutral

• Polyfill is compile-time only (<IncludeAssets>compile; analyzers</IncludeAssets>)
• No runtime performance impact (<ExcludeAssets>runtime; native; contentfiles; build; buildtransitive</ExcludeAssets>)
• Patch updates typically include performance improvements

Security Concerns ✅ Low Risk

• Well-established package from trusted maintainer (SimonCropp)
• Compile-time dependency with no runtime footprint
• Private assets configuration limits exposure
• Patch version suggests security fixes if any

Test Coverage ⚠️ Consideration

• Current State: Dependency updates typically don't require new tests
• Existing Coverage: TUnit has comprehensive test suites that would catch regressions
• Recommendation: The existing test suite should be sufficient, but consider running:

  dotnet test TUnit.Core.SourceGenerator.Tests  # As per CLAUDE.md guidelines
  dotnet test TUnit.PublicAPI                   # For API compatibility

Framework Compatibility ✅ Maintained

• Conditional inclusion logic unchanged (netstandard2.0, netstandard2.1, .NETFramework)
• Central Package Management (CPM) support maintained
• Both CPM and non-CPM project types supported

🎯 Recommendations

1. ✅ Approve: This is a safe, routine dependency update
2. ✅ Merge: No code changes required, automerge is appropriate
3. 📋 Monitor: Watch for any CI failures, though none are expected
4. 🔄 Note: The version in Directory.Packages.props:61 will need updating separately for CPM projects

📊 Risk Assessment: LOW

• Routine maintenance update
• No breaking changes
• Minimal surface area impact
• Well-tested integration patterns

---