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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.TUnit	nuget	minor	31.2.0 -> 31.3.0

---

Release Notes

VerifyTests/Verify (Verify.TUnit)

v31.3.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

Todo List:

• Analyze the changed file and understand the exact update
• Check for any breaking changes in Verify.TUnit 31.3.0
• Review security implications of the update
• Assess impact on test coverage and existing tests
• Check compatibility with the TUnit codebase
• Provide comprehensive feedback and recommendations

Review Feedback

✅ Code Quality and Best Practices

• Excellent: This is a clean, automated dependency update following best practices
• Consistent versioning: The update aligns Verify.TUnit (31.3.0) with Verify.NUnit (31.3.0), maintaining consistency across Verify packages
• Centralized dependency management: Properly using Directory.Packages.props for version management

🔒 Security Considerations

• Low Risk: Minor version update (31.2.0 → 31.3.0) from a well-established testing library
• Trusted Source: Verify.TUnit is from the reputable VerifyTests organization
• No Security Vulnerabilities: Minor version updates typically contain bug fixes and improvements, not security patches

🚀 Performance Considerations

• Minimal Impact: This is a testing utility used only during development/CI, not in production code
• Custom Implementation: The codebase uses its own VerifyTUnit wrapper (TUnit.Core.SourceGenerator.Tests/Verify.cs:194-197), which provides better control over performance characteristics
• Snapshot Testing: Used for regression testing of source generator outputs and public API changes

🧪 Test Coverage Impact

• No Regression Risk: Minor version updates in Verify packages are typically backwards compatible
• Critical for TUnit: This package is essential for:
  • API snapshot testing (TUnit.PublicAPI)
  • Source generator snapshot testing (TUnit.Core.SourceGenerator.Tests)
  • Assertion snapshot testing (TUnit.Assertions.SourceGenerator.Tests)
• Custom Integration: The custom VerifySettingsTask class provides specialized snapshot handling with file path scrubbing and normalization

🐛 Potential Issues

• None Identified:
  • Minor version bump suggests no breaking changes
  • Recent commit history shows similar updates were successful (Verify.NUnit was updated to 31.3.0 in PR chore(deps): update dependency verify.nunit to 31.3.0 #3599)
  • Custom wrapper implementation isolates the codebase from direct API changes

📋 Recommendations

1. ✅ Approve and Merge: This is a safe, routine dependency update
2. Monitor CI: The automated tests will validate compatibility with the new version
3. Snapshot Updates: If any snapshots need updating due to improved output formatting, accept those changes as they represent improvements
4. Future Consideration: Keep Verify packages aligned - consider setting up a grouped update rule in Renovate config

🎯 Conclusion

This is a well-executed, low-risk dependency update that maintains package consistency and brings potential bug fixes/improvements. The custom VerifyTUnit implementation provides good isolation from breaking changes, and the minor version bump indicates backwards compatibility.

Verdict: ✅ LGTM - Safe to merge

---

[claude]

Claude finished @thomhurst's task —— View job

---

Claude finished @thomhurst's task ——

---

PR Review: Verify.TUnit Dependency Update

Todo List:

• Analyze the changed file and understand the exact update
• Check for any breaking changes in Verify.TUnit 31.3.0
• Review security implications of the update
• Assess impact on test coverage and existing tests
• Check compatibility with the TUnit codebase
• Provide comprehensive feedback and recommendations

Review Feedback

✅ Code Quality and Best Practices

• Excellent: This is a clean, automated dependency update following best practices
• Consistent versioning: The update aligns Verify.TUnit (31.3.0) with Verify.NUnit (31.3.0), maintaining consistency across Verify packages
• Centralized dependency management: Properly using Directory.Packages.props for version management

🔒 Security Considerations

• Low Risk: Minor version update (31.2.0 → 31.3.0) from a well-established testing library
• Trusted Source: Verify.TUnit is from the reputable VerifyTests organization
• No Security Vulnerabilities: Minor version updates typically contain bug fixes and improvements, not security patches

🚀 Performance Considerations

• Minimal Impact: This is a testing utility used only during development/CI, not in production code
• Custom Implementation: The codebase uses its own VerifyTUnit wrapper (TUnit.Core.SourceGenerator.Tests/Verify.cs:194-197), which provides better control over performance characteristics
• Snapshot Testing: Used for regression testing of source generator outputs and public API changes

🧪 Test Coverage Impact

• No Regression Risk: Minor version updates in Verify packages are typically backwards compatible
• Critical for TUnit: This package is essential for:
  • API snapshot testing (TUnit.PublicAPI)
  • Source generator snapshot testing (TUnit.Core.SourceGenerator.Tests)
  • Assertion snapshot testing (TUnit.Assertions.SourceGenerator.Tests)
• Custom Integration: The custom VerifySettingsTask class provides specialized snapshot handling with file path scrubbing and normalization

🐛 Potential Issues

• None Identified:
  • Minor version bump suggests no breaking changes
  • Recent commit history shows similar updates were successful (Verify.NUnit was updated to 31.3.0 in PR chore(deps): update dependency verify.nunit to 31.3.0 #3599)
  • Custom wrapper implementation isolates the codebase from direct API changes

📋 Recommendations

1. ✅ Approve and Merge: This is a safe, routine dependency update
2. Monitor CI: The automated tests will validate compatibility with the new version
3. Snapshot Updates: If any snapshots need updating due to improved output formatting, accept those changes as they represent improvements
4. Future Consideration: Keep Verify packages aligned - consider setting up a grouped update rule in Renovate config

🎯 Conclusion

This is a well-executed, low-risk dependency update that maintains package consistency and brings potential bug fixes/improvements. The custom VerifyTUnit implementation provides good isolation from breaking changes, and the minor version bump indicates backwards compatibility.

Verdict: ✅ LGTM - Safe to merge

---