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

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

Critical Issues

None found ✅

TUnit Rules Compliance

• ✅ Dual-Mode: N/A - dependency update only
• ✅ Snapshot Testing: N/A - no source generator or API changes
• ✅ No VSTest: N/A - no test platform changes
• ✅ Performance First: N/A - compile-time only dependency
• ✅ AOT Compatible: Polyfill is correctly scoped as compile-time only

Verdict

✅ APPROVE - No critical issues

This is a straightforward minor version bump of the Polyfill package used for compile-time type generation on older frameworks. The dependency is properly scoped to compile-time only and doesn't affect runtime behavior.

[Copilot]

Pull request overview

This PR updates the Polyfill dependency from version 9.5.0 to 9.6.0 as part of routine dependency maintenance. The update is a minor version bump that should include new features or improvements without breaking changes.

Key Changes

• Updated Polyfill version reference in TUnit.Core.targets to 9.6.0

[Copilot]

The Polyfill version was updated in TUnit.Core.targets to 9.6.0, but the version in Directory.Packages.props (line 64) remains at 9.5.0. This creates an inconsistency where external NuGet consumers will use Polyfill 9.6.0 while internal development and testing will use 9.5.0. Both files should be updated together to ensure consistent behavior between development and production environments.

Suggested change

	<_TUnitPolyfillVersion>9.6.0</_TUnitPolyfillVersion>
	<_TUnitPolyfillVersion>9.5.0</_TUnitPolyfillVersion>

[thomhurst]

Summary

Updates the Polyfill dependency from version 9.5.0 to 9.6.0.

Critical Issues

None found ✅

Analysis

This is a straightforward dependency update PR from Renovate Bot. The change:

• Updates a single line in TUnit.Core/TUnit.Core.targets
• Bumps the _TUnitPolyfillVersion property from 9.5.0 to 9.6.0
• Polyfill is used for compile-time type generation on older target frameworks (netstandard2.0/2.1, .NET Framework)

TUnit rules check:

• ✅ No source generator changes → no snapshot test updates needed
• ✅ No public API changes
• ✅ No reflection or AOT concerns
• ✅ No VSTest usage
• ✅ No performance-critical code paths affected

The change follows TUnit's principle of using modern features while maintaining backward compatibility for older frameworks through polyfills.

Verdict

✅ APPROVE - No critical issues

[thomhurst]

Summary

Updates the Polyfill dependency from version 9.5.0 to 9.6.0 in TUnit.Core.targets.

Critical Issues

None found ✅

This is a straightforward dependency update:

• Changes only the version number in a single MSBuild targets file
• Does not touch source generators, reflection code, or public APIs
• Does not affect hot paths or performance-critical code
• No TUnit-specific rules are violated

Verdict

✅ APPROVE - No critical issues

This is a safe, automated dependency update by Renovate Bot. The change only updates the Polyfill package version reference used for compile-time type generation on older target frameworks (netstandard2.0, netstandard2.1, .NET Framework).