chore(deps): update dependency verify.tunit to 30.20.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.TUnit	nuget	minor	30.19.2 -> 30.20.0

---

Release Notes

VerifyTests/Verify (Verify.TUnit)

v30.20.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

---

PR Review: Verify.TUnit Dependency Update ✅

I've completed my analysis of this dependency update from Verify.TUnit 30.19.2 → 30.20.0.

Todo List:

• Read the changed file to understand the specific dependency update
• Analyze the impact of this dependency on the codebase
• Check for any usage patterns of Verify.TUnit in the project
• Review for potential breaking changes or compatibility issues
• Assess security, performance, and testing implications
• Provide comprehensive review feedback

---

Review Feedback

✅ Code Quality and Best Practices

• Clean change: This is a single-line version bump in Directory.Packages.props:90
• Proper dependency management: Using centralized package management which is a best practice
• Minor version update: Following semantic versioning, this should be backwards compatible

✅ Potential Bugs or Issues

• Low risk: Minor version bumps (30.19.2 → 30.20.0) typically maintain API compatibility
• Custom implementation: The project uses a custom Verify implementation rather than the standard Verify.TUnit library
  • Found custom VerifyTUnit classes in both /TUnit.PublicAPI/Verify.cs and /TUnit.Core.SourceGenerator.Tests/Verify.cs
  • These implement snapshot testing functionality tailored to TUnit's needs
  • The actual Verify.TUnit package may only be used for certain integrations or as a fallback

✅ Performance Considerations

• Minimal impact: Version updates in testing libraries typically don't affect runtime performance
• Test performance: The custom verify implementations handle text normalization and file I/O efficiently
• Snapshot tests: Found 130 .verified.txt files, indicating extensive snapshot testing coverage

✅ Security Concerns

• No security risks identified: Testing dependencies pose minimal security risk to production
• Trusted source: Verify is a well-established testing library from the VerifyTests organization
• Dependency scope: Only affects test projects, not production code

✅ Test Coverage

• Comprehensive coverage: Three test projects use Verify.TUnit:
  • TUnit.PublicAPI - For API surface testing
  • TUnit.Core.SourceGenerator.Tests - For source generator output verification
  • TUnit.Assertions.SourceGenerator.Tests - For assertion generator testing
• Critical testing: These snapshot tests validate public API stability and source generator output
• Custom verify logic: The project has sophisticated text scrubbing and normalization for cross-platform compatibility

🔍 Key Observations

1. Custom Implementation: The project has its own VerifyTUnit wrapper classes, suggesting the standard library is supplemented with project-specific functionality
2. Platform Compatibility: Custom verify implementations handle cross-platform path scrubbing and line ending normalization
3. API Stability Testing: Used extensively for ensuring no unintended public API changes
4. Source Generator Testing: Critical for validating generated code output remains consistent

📋 Recommendation

✅ APPROVE - This is a safe, low-risk dependency update that:

• Maintains API compatibility (minor version bump)
• Updates a testing-only dependency
• Has comprehensive test coverage to catch any issues
• Uses custom implementations that provide additional safety

The automated Renovate bot change looks good and should be merged.

---