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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.TUnit	nuget	patch	31.0.3 -> 31.0.4

---

Release Notes

VerifyTests/Verify (Verify.TUnit)

v31.0.4

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

---

Dependency Update Review: Verify.TUnit 31.0.3 → 31.0.4 ✅

Review Checklist:

• Read repository guidelines (CLAUDE.md)
• Examine the dependency change in Directory.Packages.props
• Analyze code quality and best practices
• Check for potential bugs or issues
• Evaluate performance considerations
• Review security concerns
• Assess test coverage impact

---

🔍 Review Summary

This is a safe, low-risk dependency update for a patch version bump in the Verify.TUnit testing library.

📋 Change Analysis

What Changed:

• Single line update in Directory.Packages.props:87
• Verify.TUnit version: 31.0.3 → 31.0.4
• This is a patch version update following semantic versioning

Usage in Codebase:

• Used extensively in snapshot testing across multiple test projects:
  • TUnit.PublicAPI for API surface verification
  • TUnit.Core.SourceGenerator.Tests for source generator output verification
  • TUnit.Assertions.SourceGenerator.Tests for assertion generator testing

✅ Code Quality & Best Practices

Positive aspects:

• ✅ Uses centralized package management via Directory.Packages.props
• ✅ Consistent versioning strategy across Verify packages
• ✅ Proper integration with TUnit's custom verification system

Note: The codebase includes both the standard Verify.TUnit package and a custom VerifyTUnit implementation in /TUnit.Core.SourceGenerator.Tests/Verify.cs:194, which is well-designed for handling snapshot testing with path scrubbing and normalization.

🐛 Potential Issues Assessment

Low Risk Factors:

• ✅ Patch version update (no breaking changes expected)
• ✅ Verify library is mature and stable
• ✅ No API surface changes expected in patch versions
• ✅ Existing tests will validate compatibility

Version Alignment:

• ✅ Verify core package is already at 31.0.4 (line 82)
• ⚠️ Verify.NUnit is still at 31.0.3 (line 83) - minor inconsistency but not problematic

⚡ Performance Considerations

Assessment: ✅ No Performance Impact Expected

• Patch updates typically contain bug fixes, not performance-affecting changes
• Verify library is used only in test scenarios, not production runtime
• No hot-path usage in the verification workflows

🔒 Security Assessment

Assessment: ✅ No Security Concerns

• Test-only dependency with no production runtime exposure
• Patch version unlikely to introduce security changes
• Renovate Bot provides automated security scanning

🧪 Test Coverage Impact

Assessment: ✅ Maintained Test Coverage

• Existing snapshot tests will validate the update
• Critical test areas covered:
  • /TUnit.PublicAPI/Tests.cs:38 - API surface verification
  • Source generator output verification
  • Custom verification workflows

Test Strategy Validation:

• The codebase follows TUnit guidelines requiring snapshot test acceptance after changes
• Custom VerifyTUnit implementation handles cross-platform concerns properly
• Path scrubbing and normalization prevent environment-specific test failures

---

🎯 Final Recommendation

✅ APPROVE - This is a safe, routine maintenance update.

Rationale:

1. Low risk patch version update
2. Well-tested integration points
3. Consistent with project's dependency management strategy
4. No breaking changes expected
5. Automated testing will catch any issues

Next Steps:

• The existing test suite will validate compatibility
• If snapshot tests require updates, follow the project's guidelines in CLAUDE.md to accept new snapshots
• Monitor CI for any unexpected test failures