chore(deps): update verify to 31.6.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	patch	31.6.0 -> 31.6.1
Verify.NUnit	nuget	patch	31.6.0 -> 31.6.1
Verify.TUnit	nuget	patch	31.6.0 -> 31.6.1

---

Release Notes

VerifyTests/Verify (Verify)

v31.6.1

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 these updates 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

Todo List:

• Read the changed file (Directory.Packages.props)
• Analyze the dependency changes and their impact
• Check for security/compatibility concerns
• Assess test coverage needs
• Provide final review recommendations

Detailed Analysis:

Changes Made:

• Updated 3 Verify packages in Directory.Packages.props:
  • Verify: 31.6.0 → 31.6.1
  • Verify.NUnit: 31.6.0 → 31.6.1
  • Verify.TUnit: 31.6.0 → 31.6.1

Usage Context:

• Verify packages are critical for snapshot testing in TUnit's test infrastructure
• Used in: TUnit.Core.SourceGenerator.Tests, TUnit.Assertions.SourceGenerator.Tests, TUnit.PublicAPI
• Powers verification of generated source code and public API stability
• Essential for Rule 2 (Snapshot Testing) compliance mentioned in CLAUDE.md

Patch Version Analysis (31.6.0 → 31.6.1):

• This is a patch release which should only contain bug fixes
• Release notes show minimal changes (compare link provided but no specific details)
• No breaking changes expected in patch versions

Review Feedback

✅ Code Quality & Best Practices

• APPROVED: This is a clean dependency version update using centralized package management
• Changes are properly isolated to Directory.Packages.props only
• Follows semantic versioning best practices (patch update)

✅ Security Concerns

• LOW RISK: Patch updates typically contain bug fixes and security patches
• No new dependencies introduced, only version bumps
• Verify is a well-maintained testing library from the .NET ecosystem

✅ Performance Considerations

• MINIMAL IMPACT: Patch updates rarely introduce performance regressions
• Verify is only used in test projects, not runtime code
• No performance impact on production TUnit libraries

✅ Potential Issues

• LOW RISK: Patch version updates have minimal breaking change risk
• Snapshot testing functionality is well-isolated to test projects
• Existing .verified.txt files should remain compatible

⚠️ Test Coverage Recommendations

REQUIRED: Before merging, ensure the following tests pass:

# Critical snapshot tests that use Verify
dotnet test TUnit.Core.SourceGenerator.Tests
dotnet test TUnit.PublicAPI
dotnet test TUnit.Assertions.SourceGenerator.Tests

If any snapshot tests fail, this typically means:

1. Bug fixes in Verify changed output formatting (review .received.txt files)
2. Generated source code changed due to bug fixes (validate changes are beneficial)

According to CLAUDE.md Rule 2, any snapshot test failures should be carefully reviewed before accepting.

🎯 Final Recommendation

✅ APPROVE - This is a low-risk dependency update that should be safe to merge.

Conditions:

• All automated tests must pass before merging
• Any failing snapshot tests should be manually reviewed to ensure changes are beneficial
• The Renovate Bot's automerge is appropriate for this type of change

Rationale: Patch version updates of testing dependencies are typically safe and often contain important bug fixes that improve test reliability.

---