chore(deps): update dependency polyfill to 10.7.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	patch	10.7.1 → 10.7.2

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v10.7.2

Compare Source

• #​552 Fix NET 8 CreateVersion7 polyfill RFC 9562/IETF variant bits

---

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

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

[claude]

Code Review

Verdict: LGTM — straightforward patch dependency bump, safe to merge.

Change Summary

Single-line version bump in :

-<_TUnitPolyfillVersion>10.7.1</_TUnitPolyfillVersion>
+<_TUnitPolyfillVersion>10.7.2</_TUnitPolyfillVersion>

Assessment

Correctness: The upstream patch (#552) fixes a real bug — incorrect variant bits in the Guid.CreateVersion7 polyfill for .NET 8, where the RFC 9562/IETF variant bits weren't being set correctly. This is a correctness fix worth taking.

Scope: The change is appropriately minimal — only the pinned version constant is updated. No TUnit logic is touched.

Risk: Very low. Polyfill is a compile-time source-generator package; it emits helper types rather than shipping runtime DLLs, so there is no binary compatibility surface to worry about. The fix narrows to one polyfill method that most projects won't call in tests, and the change itself is a bug-fix (making output more correct), not a breaking API change.

No prior review comments were open on this PR to verify; Codacy also reports 0 issues.

Auto-merge is already enabled — no action required.

[claude]

Code Review

Verdict: LGTM — straightforward patch dependency bump, safe to merge.

Change Summary

Single-line version bump in TUnit.Core/TUnit.Core.targets:

-<_TUnitPolyfillVersion>10.7.1</_TUnitPolyfillVersion>
+<_TUnitPolyfillVersion>10.7.2</_TUnitPolyfillVersion>

Assessment

Correctness: The upstream patch (#552) fixes a real bug — incorrect variant bits in the Guid.CreateVersion7 polyfill for .NET 8, where RFC 9562/IETF variant bits were not being set correctly. This is a meaningful correctness fix worth taking.

Scope: The change is appropriately minimal — only the pinned version constant is updated. No TUnit logic is touched.

Risk: Very low. Polyfill is a compile-time source-generator package; it emits helper types rather than shipping runtime DLLs, so there is no binary compatibility surface to worry about. The fix narrows to one polyfill method that most projects will not call in tests, and the change is a bug-fix (making output more correct), not a breaking API change.

No prior review comments were open on this PR to verify; Codacy also reports 0 issues.

Auto-merge is already enabled — no action required.