chore(deps): update dependency polyfill to 9.6.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	minor	9.5.0 → 9.6.0

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v9.6.0

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.

[thomhurst]

Summary

Minor dependency update: Polyfill package from 9.5.0 to 9.6.0.

Critical Issues

None found ✅

This is a standard dependency update that only modifies Directory.Packages.props. No TUnit-specific rules apply - no source generator, public API, or engine changes.

Verdict

✅ APPROVE - No critical issues

[Copilot]

Pull request overview

This PR updates the Polyfill NuGet package from version 9.5.0 to 9.6.0, which is a minor version bump. The update is automatically generated by Renovate Bot and includes automerge configuration. The change follows semantic versioning conventions and should be backward compatible.

Key Changes

• Polyfill package version updated from 9.5.0 to 9.6.0 in the centralized package management file

[thomhurst]

Summary

Updates the Polyfill package dependency from 9.5.0 to 9.6.0 (minor version bump).

Critical Issues

None found ✅

Analysis

This is a routine dependency update for the Polyfill library, which TUnit uses to provide compatibility APIs across different .NET versions. The change:

• Scope: Only updates the version in Directory.Packages.props (centrally managed package versioning)
• Risk: Low - minor version bump in a polyfill library should be backward-compatible
• TUnit Rules: No TUnit-specific rules apply to this change:
  • No source generator changes (no snapshot updates needed)
  • No public API changes
  • No reflection or AOT concerns
  • Not touching hot paths or core engine code
  • No VSTest dependencies

The Polyfill package is used throughout the codebase to provide modern .NET APIs on older frameworks, primarily for internal use rather than in critical hot paths.

Verdict

✅ APPROVE - No critical issues. Standard dependency maintenance.