chore(deps): update verify to 31.8.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	31.7.3 -> 31.8.0
Verify.NUnit	nuget	minor	31.7.3 -> 31.8.0
Verify.TUnit	nuget	minor	31.7.3 -> 31.8.0

---

Release Notes

VerifyTests/Verify (Verify)

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

---

PR Review: Verify Package Updates

Reviewing dependency update from Verify 31.7.3 → 31.8.0

Todo List:

• Read Directory.Packages.props to analyze the changes
• Check for any test files using Verify to understand impact
• Review for potential breaking changes or security concerns
• Assess performance implications
• Provide comprehensive feedback

Review Findings

✅ Code Quality and Best Practices

• Package Management: The PR correctly uses centralized package version management via Directory.Packages.props
• Consistency: All three Verify packages (Verify, Verify.NUnit, Verify.TUnit) are updated together to the same version (31.8.0), maintaining consistency
• Change Scope: Minimal and focused change - only updates package versions without touching any code

✅ Verify Usage Analysis

The Verify packages are actively used in the TUnit project for snapshot testing:

1. Primary Usage: TUnit.Assertions.SourceGenerator.Tests project uses Verify for snapshot testing of generated source code

   • Located in TUnit.Assertions.SourceGenerator.Tests/TestsBase.cs:158
   • Uses VerifyTUnit.Verifier for testing assertion source generator output
   • Has numerous .verified.txt files (80+ snapshot files) indicating heavy reliance on Verify

2. Test Projects Using Verify:

   • TUnit.Assertions.SourceGenerator.Tests (main usage)
   • TUnit.Core.SourceGenerator.Tests
   • TUnit.PublicAPI (API verification)

✅ Security Concerns

• Low Risk: This is a minor version update (31.7.3 → 31.8.0) from a trusted testing library
• Scope: Verify is used only in test projects, not in production code
• Dependency: No exposure to user-facing code or runtime applications

✅ Performance Considerations

• No Performance Impact: Verify is a testing-only dependency used during build/test time
• Minor Version: Unlikely to introduce performance regressions in a minor version bump
• Snapshot Testing: May include performance improvements for snapshot comparison algorithms

✅ Breaking Changes Assessment

• Minor Version: Following semantic versioning, no breaking changes expected in 31.7.3 → 31.8.0
• Test Impact: Existing .verified.txt files should remain compatible
• API Stability: No changes to verification API expected

✅ Test Coverage

• Extensive Coverage: 80+ verified snapshot files indicate comprehensive test coverage
• Continuous Testing: Renovate bot ensures updates are tested against existing test suite
• Dual Framework Support: Tests cover multiple target frameworks (.NET 4.7, .NET 8.0, .NET 9.0, .NET 10.0)

✅ Recommendation

APPROVE - This is a safe, routine dependency update that:

• ✅ Follows best practices for dependency management
• ✅ Maintains version consistency across related packages
• ✅ Has minimal risk (test-only dependency, minor version update)
• ✅ Is backed by extensive test coverage
• ✅ Uses automated testing via Renovate bot

The PR can be safely merged as automerge is appropriately enabled for this type of routine maintenance update.

---