chore(deps): update dependency polyfill to 10.1.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	minor	10.0.0 → 10.1.1

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v10.1.0

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.

[claude]

Code Review: chore(deps): update dependency polyfill to 10.1.0

This is a straightforward, automated Renovate Bot dependency bump of the Polyfill package from 10.0.0 to 10.1.0 — a minor version update.

Change Summary

The sole change is a single-line update in Directory.Packages.props (centralized package version management):

-    <PackageVersion Include="Polyfill" Version="10.0.0" />
+    <PackageVersion Include="Polyfill" Version="10.1.0" />

Assessment

No concerns. The change is safe and correct for the following reasons:

• Scope is minimal: A single-line version bump in the central Directory.Packages.props file — no logic changes, no API surface changes.
• Minor version: 10.0.0 → 10.1.0 is a minor bump. Polyfill follows a strict additive policy for minor versions (new polyfill types/members added; nothing removed), so no breaking changes are expected.
• Polyfill's role in TUnit is well-understood: The package provides backfill types (e.g., ModuleInitializerAttribute) for older TFMs. TUnit already has a MissingPolyfillAnalyzer to ensure consumers have it, and TUnit.Engine/PolyfillExtensions.cs provides a small local polyfill alongside it. A minor version bump will only ever expand the set of available APIs, not remove any.
• Centralized version management: Because ManagePackageVersionsCentrally is enabled, this single entry controls the version for all referencing projects (34 files reference Polyfill across the repo). This is the correct and only place to make this change.
• AOT / source-gen compatibility: Polyfill is a compile-time / source-generation package with no runtime assembly (it compiles polyfill types directly into the consuming assembly). A minor bump here poses no AOT risk.
• Auto-merge is configured: Renovate's automerge is enabled for this PR, which is appropriate for minor dependency updates of this kind.

Suggestions

None. This is a well-structured, low-risk dependency update that should be safe to merge.

[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

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

[claude]

Code Review: chore(deps): update dependency polyfill to 10.1.1

This is a follow-up to my previous review (which assessed the bump to 10.1.0). The PR has since been updated by Renovate to target 10.1.1.

Change Summary

Single-line version bump in Directory.Packages.props:

-    <PackageVersion Include="Polyfill" Version="10.0.0" />
+    <PackageVersion Include="Polyfill" Version="10.1.1" />

Assessment

No concerns. My earlier analysis remains fully applicable:

• Patch bump on top of minor: 10.1.0 → 10.1.1 is a patch release — strictly bug-fix territory, making this even lower risk than the previous 10.1.0 bump.
• No breaking changes: Polyfill's patch releases only ship fixes to existing polyfill implementations, never API removals.
• Scope unchanged: Still a single-line edit to the centralized version file; all 34+ referencing projects pick up the change automatically via Central Package Management.
• AOT / source-gen safety: Polyfill is a compile-time package — patch bumps here carry no runtime or AOT risk.

Conclusion

Safe to merge. Automerge is appropriate for this class of update.

[claude]

Code Review

This is a Renovate Bot dependency update bumping Polyfill from 10.0.0 to 10.1.1 (a minor version bump).

Change: Directory.Packages.props — single line version string update.

Assessment

Nothing to flag here. This is a straightforward, low-risk minor version bump of the Polyfill package:

• Minor version bump (10.0.0 → 10.1.1) follows semver, so no breaking changes expected.
• The Polyfill package provides source-level polyfills for newer .NET APIs — it has no runtime dependency and is compile-time only, so the blast radius of any regression is limited to build-time.
• The change is isolated to the central Directory.Packages.props version catalog, which is the correct place for it (this repo uses CPM — Central Package Management).
• Automerge is enabled on this PR, which is appropriate for this category of low-risk dependency update.

Verdict

Looks good. Safe to merge.

[claude]

Code Review

This is a Renovate Bot dependency update bumping Polyfill from 10.0.0 to 10.1.1 (a minor version bump).

Change: Directory.Packages.props — single line version string update.

Assessment

Nothing to flag here. This is a straightforward, low-risk minor version bump of the Polyfill package:

• Minor version bump (10.0.0 → 10.1.1) follows semver, so no breaking changes expected.
• The Polyfill package provides source-level polyfills for newer .NET APIs — it has no runtime dependency and is compile-time only, so the blast radius of any regression is limited to build-time.
• The change is isolated to the central Directory.Packages.props version catalog, which is the correct place for it (this repo uses CPM — Central Package Management).
• Automerge is enabled on this PR, which is appropriate for this category of low-risk dependency update.

Verdict

Looks good. Safe to merge.