chore(deps): update dependency polyfill to v11

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	major	10.11.2 → 11.0.0

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v11.0.0

Compare Source

• #​567 Retire stream-wrapper polyfills for net11
• #​568 Add Process.TryGetProcessById and silent param on Run/RunAsync

---

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.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 72dd486ba1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep the packaged Polyfill injection in sync

This bump only affects this repo's central package version and the template, but the TUnit.Core NuGet package still packs TUnit.Core.targets, where _TUnitPolyfillVersion remains 10.11.2 (TUnit.Core/TUnit.Core.targets:11). Any .NET Framework/netstandard consumer relying on TUnit's automatic polyfill injection will continue restoring 10.11.2, so the dependency update is not actually applied for that supported path.

Useful? React with 👍 / 👎.

[claude]

Review: Polyfill 10.11.2 → 11.0.0 (Renovate)

This is a minimal, mechanical dependency bump — the version string is updated consistently in both Directory.Packages.props (central package version) and TUnit.Templates/content/TUnit/TestProject.csproj (the net48 template reference). No other code changes. Nothing architectural to flag here since there's no hand-written logic in the diff.

Notes for merging safely:

• Polyfill is a compile-time-only source-inlining analyzer package (no runtime dependency shipped), so the blast radius of a bad bump is a build break, not a runtime regression — low risk.
• It is still a major version bump (10.x → 11.0.0), and the package was published today with essentially no changelog available yet upstream. Since TUnit multi-targets net8.0;net9.0;net10.0 plus the net48 template, I'd hold off merging until CI (build across all TFMs + snapshot tests) is fully green rather than relying on automerge purely because it's a patch-looking version-string diff.
• No previously open review comments on this PR to reconcile against.

Looks good to merge once CI passes. No changes requested.