chore(deps): update dependency polyfill to 8.8.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Polyfill	nuget	minor	8.7.4 -> 8.8.0

---

Release Notes

SimonCropp/Polyfill (Polyfill)

v8.8.0

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]

Claude finished @thomhurst's task —— View job

---

Pull Request Review

I've thoroughly reviewed this dependency update from Polyfill 8.7.4 to 8.8.0. Here's my comprehensive analysis:

Todo List:

• Read the changed file to understand the dependency update
• Research the Polyfill library and what changed in version 8.8.0
• Check how Polyfill is used in the codebase
• Assess potential impact and compatibility issues
• Provide comprehensive review feedback

Review Feedback

✅ Code Quality & Best Practices

• The dependency update follows proper practices with centralized package management in Directory.Packages.props
• Polyfill is correctly configured as a build-time only dependency with <PrivateAssets>all</PrivateAssets>
• The package includes appropriate assets: runtime; build; native; contentfiles; analyzers; buildtransitive

✅ Security Assessment

• Low Risk: This is a minor version bump (8.7.4 → 8.8.0) from a well-established library by Simon Cropp
• The Polyfill library provides backward compatibility polyfills for modern .NET APIs on older frameworks
• No security concerns identified with this update

✅ Performance Considerations

• Positive Impact: Polyfill typically improves performance by providing optimized implementations
• Since it's a build-time dependency with <PrivateAssets>all</PrivateAssets>, it won't affect runtime dependencies
• The library provides efficient file I/O operations that the codebase actively uses

✅ Compatibility & Usage Analysis

The codebase makes extensive use of Polyfill APIs:

File Operations (TUnit.PublicAPI/Verify.cs:132, TUnit.PublicAPI/Tests.cs:54-55):

await FilePolyfill.ReadAllTextAsync(pair.ReceivedPath);
await FilePolyfill.WriteAllTextAsync(_receivedPath, NormalizeNewline(final));

Test Infrastructure (multiple test files):

• Used in before/after test hooks for file operations
• Critical for test verification and snapshot testing functionality

Custom Extensions (TUnit.Engine/PolyfillExtensions.cs:5-10):

• Custom ReplaceLineEndings method that doesn't depend on Polyfill internals
• Safe from breaking changes

✅ Test Coverage Assessment

• Recommendation: Run the full test suite, particularly:
  • dotnet test TUnit.PublicAPI (for API verification functionality)
  • dotnet test TUnit.Core.SourceGenerator.Tests (if file I/O is used in snapshots)
• The file I/O operations are used in critical verification logic, so thorough testing is essential

🟡 Minor Recommendations

1. Testing: While this is a minor update that should be safe, verify that snapshot testing and file verification functionality works correctly
2. Monitoring: Keep an eye on any file I/O related issues in CI/CD after merge

Final Assessment

✅ APPROVED - This is a safe, low-risk dependency update that should be merged. The minor version bump indicates backward compatibility, and the codebase usage patterns are stable and well-established.

The Polyfill library is essential for TUnit's cross-framework compatibility and file operations. This update likely includes bug fixes and performance improvements without breaking changes.

[claude]

Claude finished @thomhurst's task —— View job

---

Pull Request Review

I've thoroughly reviewed this dependency update from Polyfill 8.7.4 to 8.8.0. Here's my comprehensive analysis:

Todo List:

• Read the changed file to understand the dependency update
• Research the Polyfill library and assess the version change impact
• Check how Polyfill is used in the codebase
• Analyze for code quality, bugs, performance, and security concerns
• Assess test coverage requirements
• Provide comprehensive review feedback

Review Feedback

✅ Code Quality & Best Practices

• The dependency update follows proper practices with centralized package management in Directory.Packages.props:61-64
• Polyfill is correctly configured as a build-time only dependency with <PrivateAssets>all</PrivateAssets>
• The package includes appropriate assets: runtime; build; native; contentfiles; analyzers; buildtransitive

✅ Security Assessment

• Low Risk: This is a minor version bump (8.7.4 → 8.8.0) from a well-established library by Simon Cropp
• The Polyfill library provides backward compatibility polyfills for modern .NET APIs on older frameworks
• No security concerns identified with this update

✅ Performance Considerations

• Positive Impact: Polyfill typically improves performance by providing optimized implementations
• Since it's a build-time dependency with <PrivateAssets>all</PrivateAssets>, it won't affect runtime dependencies
• The library provides efficient file I/O operations that the codebase actively uses

✅ Compatibility & Usage Analysis

The codebase makes extensive use of Polyfill APIs:

File Operations (TUnit.PublicAPI/Verify.cs:132, TUnit.PublicAPI/Tests.cs:54-55):

await FilePolyfill.ReadAllTextAsync(pair.ReceivedPath);
await FilePolyfill.WriteAllTextAsync(_receivedPath, NormalizeNewline(final));

Test Infrastructure (multiple test files):

• Used in before/after test hooks for file operations
• Critical for test verification and snapshot testing functionality

Custom Extensions (TUnit.Engine/PolyfillExtensions.cs:5-10):

• Custom ReplaceLineEndings method that doesn't depend on Polyfill internals
• Safe from breaking changes

✅ Test Coverage Assessment

• Recommendation: Run the full test suite, particularly:
  • dotnet test TUnit.PublicAPI (for API verification functionality)
  • dotnet test TUnit.Core.SourceGenerator.Tests (if file I/O is used in snapshots)
• The file I/O operations are used in critical verification logic, so thorough testing is essential

🟡 Minor Recommendations

1. Testing: While this is a minor update that should be safe, verify that snapshot testing and file verification functionality works correctly
2. Monitoring: Keep an eye on any file I/O related issues in CI/CD after merge

Final Assessment

✅ APPROVED - This is a safe, low-risk dependency update that should be merged. The minor version bump indicates backward compatibility, and the codebase usage patterns are stable and well-established.

The Polyfill library is essential for TUnit's cross-framework compatibility and file operations. This update likely includes bug fixes and performance improvements without breaking changes.