chore(deps): update dependency polyfill to 9.3.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	patch	9.3.1 -> 9.3.2

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v9.3.2

Compare Source

---

Configuration

📅 Schedule: 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]

PR Review: Polyfill Dependency Update (9.3.1 → 9.3.2)

✅ Overall Assessment: APPROVED

This is a straightforward patch version bump for the Polyfill dependency managed by Renovate Bot. The change is minimal and low-risk.

---

📋 Review Summary

Change Analysis:

• File Modified: TUnit.Core/TUnit.Core.targets
• Type: Patch version update (9.3.1 → 9.3.2)
• Scope: Updates the _TUnitPolyfillVersion property used for automatic Polyfill injection in legacy frameworks

Code Quality: ✅ PASS

• Single-line change with clear intent
• Follows existing pattern and style
• No deviation from project conventions

Potential Issues: ✅ NONE IDENTIFIED

• Patch updates typically contain bug fixes and non-breaking changes
• No breaking API changes expected
• Polyfill is a compile-time dependency (PrivateAssets, IncludeAssets)
• Only affects projects targeting: netstandard2.0, netstandard2.1, or .NET Framework

Performance Considerations: ✅ NO IMPACT

• Polyfill is excluded from runtime (ExcludeAssets: runtime)
• Used only for compile-time type generation
• No runtime performance implications

Security Concerns: ✅ NO CONCERNS

• Minor patch update from established dependency
• Polyfill has no runtime footprint in the shipped library
• Automated Renovate PR with standard update pattern

Test Coverage: ⚠️ RECOMMENDATION

• Change should be validated by existing CI/CD pipeline
• No new tests required (dependency update only)
• Recommendation: Verify CI passes before merge (particularly for netstandard2.0/2.1 and .NET Framework targets)

---

🎯 TUnit-Specific Considerations

Per CLAUDE.md guidelines:

1. Dual-Mode Implementation: ✅ N/A (dependency update only)
2. Snapshot Testing: ✅ N/A (no source generator or public API changes)
3. AOT/Trimming Compatibility: ✅ Safe (compile-time only dependency)
4. Performance First: ✅ No impact (compile-time only)
5. Modern C# Syntax: ✅ N/A (build configuration change)

Context: This update maintains the automatic Polyfill injection mechanism introduced to resolve issues like #3731 and #2734, which provide compile-time polyfills for modern C# features when targeting legacy frameworks.

---

✅ Recommendation

APPROVE and MERGE once CI passes. This is a safe, automated dependency update that:

• Follows semantic versioning (patch update)
• Maintains compatibility with existing functionality
• Leverages Renovate Bot's automated testing
• Includes proper automerge configuration

The automerge flag is appropriate for this type of change. No additional action required beyond CI validation.

[Copilot]

Pull request overview

This PR updates the Polyfill NuGet package dependency from version 9.3.1 to 9.3.2, a patch-level maintenance update.

Key Change:

• Updates the _TUnitPolyfillVersion property in TUnit.Core.targets from 9.3.1 to 9.3.2

[Copilot]

The Polyfill version update is incomplete. While this file has been updated to 9.3.2, the Directory.Packages.props file still references version 9.3.1 on line 62. This creates a version mismatch between the two configuration files. The Directory.Packages.props file should also be updated to use version 9.3.2 for consistency.

[claude]

PR Review: Polyfill Dependency Update

⚠️ Critical Issue: Incomplete Version Update

The PR updates the Polyfill version in TUnit.Core.targets but misses updating Directory.Packages.props, creating a version mismatch:

Files with version discrepancy:

• ✅ TUnit.Core/TUnit.Core.targets:11 - Updated to 9.3.2
• ❌ Directory.Packages.props:62 - Still at 9.3.1 (needs update)

Why This Matters

TUnit uses Central Package Management (CPM) via Directory.Packages.props. While TUnit.Core.targets uses VersionOverride to inject Polyfill for downstream consumers, the TUnit codebase itself references the version in Directory.Packages.props. This mismatch could cause:

1. Build inconsistencies across different project configurations
2. Confusion for developers working on TUnit (seeing two different versions)
3. Potential issues in projects using both files

Required Fix

Update Directory.Packages.props line 62:

-    <PackageVersion Include="Polyfill" Version="9.3.1" />
+    <PackageVersion Include="Polyfill" Version="9.3.2" />

Additional Observations

✅ Good:

• The change itself is minimal and low-risk (patch version bump)
• PR is properly automated via Renovate Bot
• No breaking changes expected from Polyfill 9.3.1 → 9.3.2

ℹ️ Note:

• The Polyfill package is used for compile-time polyfills for older .NET targets (netstandard2.0/2.1, .NET Framework)
• It's included as PrivateAssets with only compile-time assets, so no runtime impact
• This is a transitive dependency managed by TUnit's build system

Recommendation

Action Required: Update Directory.Packages.props to maintain version consistency across the codebase. The Renovate Bot likely only scanned one file due to the custom _TUnitPolyfillVersion property usage.

---

Reviewed according to TUnit development guidelines (CLAUDE.md)

[claude]

PR Review: Polyfill Dependency Update (9.3.1 → 9.3.2)

✅ Overall Assessment: APPROVED

This is a straightforward patch-level dependency update managed by Renovate Bot. The change is minimal and low-risk.

---

📋 Review Details

Change Summary

• File Modified: TUnit.Core/TUnit.Core.targets
• Update Type: Patch version bump (9.3.1 → 9.3.2)
• Scope: Single line change updating the _TUnitPolyfillVersion property

Code Quality ✅

• Clean, minimal change
• Follows existing formatting and conventions
• No impact on code structure or logic

Compatibility & Risk ✅

• Patch-level update (9.3.x) - typically backward compatible
• Polyfill is used for compile-time type generation for legacy frameworks (netstandard2.0/2.1, .NET Framework)
• No breaking changes expected in patch releases
• Change is isolated to dependency version string

Testing Considerations ✅

• CI should validate this change automatically
• Polyfill changes typically don't require new tests in TUnit itself
• The dependency is consumed at compile-time only (PrivateAssets>all, IncludeAssets>compile; analyzers)

Performance ✅

• No performance impact (compile-time only dependency)
• No runtime implications

Security ✅

• Patch updates often include security fixes
• Coming from a trusted source (SimonCropp/Polyfill)
• Renovate Bot ensures timely dependency updates

---

📝 Notes

1. Automerge: This PR has automerge enabled, which is appropriate for patch-level dependency updates
2. No Manual Changes Needed: The change is correct as-is
3. Polyfill Purpose: This dependency provides modern C# language features for older target frameworks, consistent with TUnit's goal of supporting modern syntax across all platforms

---

✅ Recommendation

Approve and merge once CI passes. This is a routine maintenance update that keeps TUnit's dependencies current.

---

Review performed by Claude Code following TUnit development guidelines

[claude]

✅ Pull Request Review: Polyfill 9.3.1 → 9.3.2

Summary

This is an automated Renovate bot PR that updates the Polyfill dependency from version 9.3.1 to 9.3.2 (patch version bump).

Code Quality ✅

Excellent - The change follows TUnit's conventions:

• Changes are in the correct location (TUnit.Core/TUnit.Core.targets)
• Uses the established _TUnitPolyfillVersion property pattern
• Maintains consistency with the project's MSBuild targets architecture

Changes Analysis

Modified Files:

• TUnit.Core/TUnit.Core.targets:11 - Version property updated from 9.3.1 to 9.3.2

What's NOT Changed (Important):

• ❗ Directory.Packages.props:62 still references 9.3.1 - This appears to be a missing update

Issues Identified 🔴

1. Incomplete Update (BLOCKER)

The PR updates TUnit.Core.targets but does not update Directory.Packages.props which also defines Polyfill version:

<!-- Directory.Packages.props line 62 - Still at 9.3.1 -->
<PackageVersion Include="Polyfill" Version="9.3.1" />

Impact: Since TUnit uses Central Package Management (ManagePackageVersionsCentrally=true), the version in Directory.Packages.props takes precedence. This means:

• Projects with CPM will still use 9.3.1 (from Directory.Packages.props)
• Only non-CPM projects will attempt to use 9.3.2 (from TUnit.Core.targets)
• This creates version inconsistency across the codebase

Recommendation: Update both locations to 9.3.2.

Risk Assessment 🟡

Low Risk - This is a patch version update which typically includes:

• Bug fixes only
• No breaking changes expected
• No new features

However, the incomplete update creates consistency risk.

Performance Considerations ✅

No performance impact - Polyfill is a compile-time only dependency (<IncludeAssets>compile; analyzers</IncludeAssets>).

Security Considerations ✅

No security concerns - Polyfill provides backported C# language features at compile-time.

Test Coverage ⚠️

Recommendation: After fixing the version inconsistency, verify:

1. Build succeeds: dotnet build
2. All tests pass: dotnet test
3. No snapshot updates needed (unlikely for dependency-only change)
4. AOT compatibility maintained (if applicable)

Required Actions 🔧

Before Merge:

1. ✅ Update TUnit.Core.targets:11 (already done)
2. ❌ Update Directory.Packages.props:62 to version 9.3.2
3. ⚠️ Run full test suite to verify
4. ⚠️ Verify no breaking changes in Polyfill 9.3.2 release notes

Suggested Fix

--- a/Directory.Packages.props
+++ b/Directory.Packages.props
@@ -59,7 +59,7 @@
     <PackageVersion Include="OneOf" Version="3.0.271" />
     <PackageVersion Include="OneOf.SourceGenerator" Version="3.0.271" />
     <PackageVersion Include="Polly" Version="8.6.5" />
-    <PackageVersion Include="Polyfill" Version="9.3.1" />
+    <PackageVersion Include="Polyfill" Version="9.3.2" />
     <PackageVersion Include="PublicApiGenerator" Version="11.5.4" />

---

Verdict: ⚠️ Changes Requested - The update is incomplete. Both package version definitions must be updated to maintain consistency.