chore(deps): update dependency polyfill to 9.24.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	patch	9.24.0 → 9.24.1

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v9.24.1

Compare Source

---

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 Renovate Bot.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[claude]

Code Review

This is a Renovate Bot automated dependency update bumping Polyfill from → (patch release).

Change Summary

Single-line change in TUnit.Core/TUnit.Core.targets:

• <_TUnitPolyfillVersion>9.24.0</_TUnitPolyfillVersion> → <_TUnitPolyfillVersion>9.24.1</_TUnitPolyfillVersion>

Assessment

Looks good. This is a straightforward patch version bump for the SimonCropp/Polyfill package, which is used to provide compile-time polyfills for older target frameworks (netstandard2.0, netstandard2.1, and .NETFramework). Patch releases are generally safe — no API changes expected.

No architectural concerns, no logic changes, no behavioral risk. Safe to merge.

[claude]

Code Review

This is a Renovate Bot automated dependency update bumping Polyfill from 9.24.0 to 9.24.1 (patch release).

Change Summary

Single-line change in TUnit.Core/TUnit.Core.targets:

• _TUnitPolyfillVersion bumped from 9.24.0 to 9.24.1

Assessment

Looks good. This is a straightforward patch version bump for the SimonCropp/Polyfill package, which provides compile-time polyfills for older target frameworks (netstandard2.0, netstandard2.1, and .NETFramework). Patch releases are generally safe — no API changes expected.

No architectural concerns, no logic changes, no behavioral risk. Safe to merge.