chore(deps): update dependency polyfill to 10.7.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	patch	10.7.0 → 10.7.1

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v10.7.1

Compare Source

• #​551 perf: replace array creation with stackalloc

---

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 ✅

🟢 Issues0 issues

Results:
0 new issues

View in Codacy

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

[claude]

Code Review

This is a Renovate-generated patch bump of the package from → . The sole change in is a performance improvement that replaces heap array creation with stackalloc internally (PR #551).

Bug: TUnit.Core.targets was not updated — consumers still receive 10.7.0

File:TUnit.Core/TUnit.Core.targets, line 11

<_TUnitPolyfillVersion>10.7.0</_TUnitPolyfillVersion> <!-- should be 10.7.1 -->

TUnit.Core.targets is a shipped MSBuild targets file embedded in the TUnit.Core NuGet package. It injects Polyfill into consumers automatically for netstandard2.0, netstandard2.1, and .NETFramework targets. Both non-CPM projects (line 17) and CPM projects (line 26 via VersionOverride) use this hardcoded _TUnitPolyfillVersion value.

Result of this miss: TUnit's own internal tests compile against 10.7.1 (from Directory.Packages.props), but every downstream NuGet consumer of TUnit.Core on the affected target frameworks gets 10.7.0 injected. The PR's stated upgrade is never exercised on the consumer-facing code path.

Fix: Update line 11 of TUnit.Core/TUnit.Core.targets:

<_TUnitPolyfillVersion>10.7.1</_TUnitPolyfillVersion>

---

Other things checked (not issues)

• stackalloc AOT/unsafe safety: Polyfill 10.7.1 uses only Span-based stackalloc (e.g., Span<byte> x = stackalloc byte[16]), not pointer-based syntax. No AllowUnsafeBlocks requirement is introduced for consumers.
• Source generator stack overflow risk: The two stackalloc-containing methods (RandomNumberGenerator.GetHexString, Guid.CreateVersion7) are never called by TUnit's source generators — refuted after code tracing.
• The version bump itself is low-risk: patch version, pure performance optimization, no API surface change.

[claude]

Code Review

This is a Renovate-generated patch bump of the Polyfill package from 10.7.0 to 10.7.1. The sole change in 10.7.1 is a performance improvement that replaces heap array creation with stackalloc internally.

Bug: TUnit.Core.targets was not updated — consumers still receive 10.7.0

File:TUnit.Core/TUnit.Core.targets, line 11

<_TUnitPolyfillVersion>10.7.0</_TUnitPolyfillVersion> <!-- should be 10.7.1 -->

TUnit.Core.targets is a shipped MSBuild targets file embedded in the TUnit.Core NuGet package. It injects Polyfill into consumers automatically for netstandard2.0, netstandard2.1, and .NETFramework targets. Both non-CPM projects (line 17) and CPM projects (line 26 via VersionOverride) use this hardcoded _TUnitPolyfillVersion value.

Result of this miss: TUnit's own internal tests compile against 10.7.1 (from Directory.Packages.props), but every downstream NuGet consumer of TUnit.Core on the affected target frameworks gets 10.7.0 injected. The PR's stated upgrade is never exercised on the consumer-facing code path.

Fix: Update line 11 of TUnit.Core/TUnit.Core.targets:

<_TUnitPolyfillVersion>10.7.1</_TUnitPolyfillVersion>

---

Other things checked (not issues)

• stackalloc AOT/unsafe safety: Polyfill 10.7.1 uses only Span-based stackalloc (e.g., Span<byte> x = stackalloc byte[16]), not pointer-based syntax. No AllowUnsafeBlocks requirement is introduced for consumers.
• Source generator stack overflow risk: The two stackalloc-containing methods (RandomNumberGenerator.GetHexString, Guid.CreateVersion7) are never called by TUnit's source generators — refuted after code tracing.
• The version bump itself is low-risk: patch version, pure performance optimization, no API surface change.