chore(deps): update dependency polyfill to 11.4.3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	patch	11.4.2 → 11.4.3

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v11.4.3

Compare Source

• #​615 ConditionalWeakTable.Remove(key, out value) polyfill causes IL2091
• #​616 Annotate TValue on ConditionalWeakTable.Remove polyfill to fix IL2091

---

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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-05T09:00:56.820958Z	81cbeff	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 11bc01df-2985-4aae-b0f9-f39d662c1634

📥 Commits

Reviewing files that changed from the base of the PR and between 0d55e02 and 81cbeff.

📒 Files selected for processing (2)

• Directory.Packages.props
• src/TUnit.Templates/content/TUnit/TestProject.csproj

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The centrally managed Polyfill version and the .NET Framework template project reference change from 11.4.2 to 11.4.3. The template reference retains its existing PrivateAssets="all" setting.

Changes

Polyfill package version

Layer / File(s)	Summary
Update Polyfill versions Directory.Packages.props, src/TUnit.Templates/content/TUnit/TestProject.csproj	Both package version declarations change from 11.4.2 to 11.4.3. The template reference retains PrivateAssets="all".

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 81cbe

No material issue is evident in this dependency update; it appears ready to merge subject to normal checks.

Architecture Summary

Architecture risk: 🔵 Low · up to 81cbe

The change affects 2 systems.

Changed systems: Directory.Packages.props, src

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — Directory.Packages.props (service) was modified; 1 changed file maps to changed impact.
• observed — src (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in Directory.Packages.props: The Polyfill package version changes from 11.4.2 to 11.4.3.
• observed — Modified behavior in src/TUnit.Templates/content/TUnit/TestProject.csproj: The .NET Framework-only Polyfill package reference changes from version 11.4.2 to 11.4.3; PrivateAssets remains all.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely identifies the Polyfill dependency update to version 11.4.3.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the package line,
And finds the version set to nine—
Wait, eleven point four point three,
Now both references match with glee.
It hops away beneath the moon.}

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 4/5

[High risk] Updates a shared polyfill dependency across the project.

The PR appears safe to merge, with a non-blocking gap in validation of the generated .NET Framework template.

Findings

1.  Template dependency lacks build coverage ▶

Summary

Updates Polyfill from 11.4.2 to 11.4.3 for centrally managed projects and the .NET Framework TUnit project template.

• Both explicit version pins remain aligned.
• Generated .NET Framework template projects are not built by the identified template validation path.

_{Reviews (1) · Last reviewed commit: "chore(deps): update dependency polyfill ..."}

[greptile-apps]

Template dependency lacks build coverage
The updated Polyfill version is used when the template generates a .NET Framework project, but the net48 template test removes package versions from its snapshot and the template pipeline only creates projects without building them. A restore or build problem with this version could therefore go undetected until someone uses the generated project. Consider adding a restore/build check for a generated .NET Framework project.

Knowledge Base Used: Observability, ecosystem extensions, and delivery

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!