chore(deps): update verify to 31.9.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	patch	31.9.1 → 31.9.2
Verify.NUnit	nuget	patch	31.9.1 → 31.9.2
Verify.TUnit	nuget	patch	31.9.1 → 31.9.2

---

Release Notes

VerifyTests/Verify (Verify)

v31.9.2

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]

PR Review: Verify Package Update (31.9.1 → 31.9.2)

✅ Overall Assessment: APPROVED

This is a straightforward dependency patch update from Renovate Bot that updates three Verify-related packages.

---

📋 Review Summary

Changed Files: 1 (Directory.Packages.props)
Impact: Low-risk patch version update
Type: Dependency maintenance

---

✅ Positive Aspects

1. Proper Scope: The update affects snapshot testing dependencies (Verify, Verify.NUnit, Verify.TUnit) used in:

   • TUnit.Core.SourceGenerator.Tests (snapshot tests per Rule 2 in CLAUDE.md)
   • TUnit.PublicAPI (API snapshot tests per Rule 2)
   • TUnit.Assertions.SourceGenerator.Tests

2. Version Consistency: All three Verify packages are updated in lockstep (31.9.1 → 31.9.2), maintaining version alignment.

3. Patch Version: This is a patch release (x.x.X), suggesting bug fixes only with minimal risk of breaking changes.

4. Automated Testing: CI checks are in progress to validate the update across multiple platforms (ubuntu, windows, macos) and locales (fr-FR, pl-PL, de-DE).

5. Central Package Management: Uses Directory.Packages.props for centralized version management, which is a best practice for multi-project repositories.

---

🔍 Considerations

Snapshot Testing Impact (CRITICAL - Per CLAUDE.md Rule 2):

Since this update affects the Verify library used for snapshot tests, there is a possibility that:

• Generated snapshots might have format changes
• Snapshot comparison logic might behave differently

Recommended Action After CI Passes:

# Run snapshot tests locally to verify no unexpected changes
dotnet test TUnit.Core.SourceGenerator.Tests
dotnet test TUnit.PublicAPI
dotnet test TUnit.Assertions.SourceGenerator.Tests

# If any .received.txt files are generated, review them carefully
# Only accept if changes are expected/acceptable

---

🎯 CLAUDE.md Compliance

Rule	Status	Notes
Rule 1: Dual-Mode	✅ N/A	Dependency update only
Rule 2: Snapshot Testing	⚠️ Monitor	May affect snapshot behavior
Rule 3: No VSTest	✅ Pass	No VSTest references
Rule 4: Performance	✅ Pass	No performance impact expected
Rule 5: AOT/Trimming	✅ Pass	Test-only dependency

---

🚦 Recommendations

1. Monitor CI Results: Wait for all CI checks to complete successfully, especially:

   • .NET workflow (cross-platform tests)
   • Locale Test workflow (ensures no culture-specific issues)

2. Check for Snapshot Changes: After merge, watch for any snapshot test failures in subsequent PRs that might indicate behavioral changes in Verify.

3. Auto-merge Safety: The PR has auto-merge enabled, which is appropriate for patch-level dependency updates with comprehensive CI coverage.

---

📝 Minor Notes

• No code quality issues (no code changes)
• No security concerns (patch update from trusted source)
• No performance considerations (test dependency only)
• No test coverage gaps (existing tests will validate)

---

✅ Verdict

LGTM - This is a safe, well-managed dependency update. The change is minimal, properly scoped, and protected by comprehensive CI checks. Once CI passes, this can be safely merged.

The only watch point is potential snapshot test changes, but the CI will catch any issues before merge.

---

Review conducted according to TUnit CLAUDE.md guidelines v2.0