chore(deps): update dependency polyfill to 10.11.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	patch	10.11.1 → 10.11.2

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v10.11.2

Compare Source

• #​566 Fix issues where code diverged from bcl behavior

---

Configuration

📅 Schedule: (UTC)

• 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 Mend Renovate.

[claude]

Code Review: Polyfill patch update (10.11.1 → 10.11.2)

This is a single-line patch bump in TUnit.Core/TUnit.Core.targets updating _TUnitPolyfillVersion from 10.11.1 to 10.11.2.

Assessment: ✅ Looks good, no concerns.

What's changing

The v10.11.2 release fixes cases where Polyfill's generated code diverged from BCL behavior (#566). This is a correctness fix, not an API change, so it's safe to take.

Why this is correct

• Polyfill is used here only for compile-time type generation on older TFMs (netstandard2.0, netstandard2.1, .NETFramework); it has no runtime impact on the primary net8/9/10 targets.
• Patch version per semver — no breaking API changes expected.
• Bringing Polyfill closer to BCL behavior reduces the risk of subtle test-correctness differences when running TUnit on older frameworks.

No architectural concerns. Automerge is appropriate for this class of dependency update.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{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.}