chore(deps): update verify to 31.7.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	patch	31.7.1 -> 31.7.2
Verify.NUnit	nuget	patch	31.7.1 -> 31.7.2
Verify.TUnit	nuget	patch	31.7.1 -> 31.7.2

---

Release Notes

VerifyTests/Verify (Verify)

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

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Package Updates ✅

Comprehensive review completed for this dependency update PR.

Review Checklist:

• Examine the changed files and dependency updates
• Assess security implications of the version bump
• Check for potential breaking changes or compatibility issues
• Evaluate performance considerations
• Review test coverage requirements
• Provide final recommendation

---

📋 Review Summary

Overall Assessment: ✅ APPROVED - This is a safe dependency update.

🔍 Code Quality & Changes

Files Changed:

• Directory.Packages.props:84,85,89 - Clean version bumps for Verify packages

Change Analysis:

• Verify: 31.7.1 → 31.7.2 (patch version)
• Verify.NUnit: 31.7.1 → 31.7.2 (patch version)
• Verify.TUnit: 31.7.1 → 31.7.2 (patch version)

The changes are minimal, well-formatted, and follow the project's centralized package management pattern.

🔒 Security Assessment

Risk Level: ✅ LOW

• Minor patch version update from a trusted, well-maintained verification library
• No security vulnerabilities identified in this version bump
• Package source is legitimate (VerifyTests/Verify GitHub repository)

⚡ Performance Considerations

Impact: ✅ MINIMAL

• Patch version updates typically contain only bug fixes
• No performance regressions expected from verification library updates
• TUnit's custom snapshot testing implementation (TUnit.PublicAPI/Verify.cs, TUnit.Core.SourceGenerator.Tests/Verify.cs) is unaffected

🧪 Test Coverage & Compatibility

Analysis:

• TUnit uses both the external Verify packages AND custom snapshot testing implementations
• External packages used in:
  • TUnit.Assertions.SourceGenerator.Tests
  • TUnit.Core.SourceGenerator.Tests
  • TUnit.PublicAPI
• Custom implementations provide project-specific snapshot testing functionality
• Patch versions maintain backward compatibility

Test Requirements:
According to CLAUDE.md, snapshot tests should be run when dependency changes might affect verification:

dotnet test TUnit.Core.SourceGenerator.Tests
dotnet test TUnit.PublicAPI

🚨 Potential Issues

None identified - This is a routine dependency maintenance update with:

• No breaking changes (patch version)
• No API changes expected
• Minimal risk profile

✅ Recommendation

APPROVE and MERGE - This PR is ready for integration:

1. Safe Update: Patch version with no breaking changes
2. Automated Testing: CI will validate compatibility
3. Low Risk: Minimal impact on TUnit's functionality
4. Good Practice: Keeping dependencies current for security and stability

Note for Maintainers: Consider running the snapshot test suites (TUnit.Core.SourceGenerator.Tests and TUnit.PublicAPI) if any unexpected verification behavior is observed post-merge, though this is unlikely with a patch update.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify Package Updates ✅

Comprehensive review completed for this dependency update PR.

Review Checklist:

• Examine the changed files and dependency updates
• Assess security implications of the version bump
• Check for potential breaking changes or compatibility issues
• Evaluate performance considerations
• Review test coverage requirements
• Provide final recommendation

---

📋 Review Summary

Overall Assessment: ✅ APPROVED - This is a safe dependency update.

🔍 Code Quality & Changes

Files Changed:

• Directory.Packages.props:84,85,89 - Clean version bumps for Verify packages

Change Analysis:

• Verify: 31.7.1 → 31.7.2 (patch version)
• Verify.NUnit: 31.7.1 → 31.7.2 (patch version)
• Verify.TUnit: 31.7.1 → 31.7.2 (patch version)

The changes are minimal, well-formatted, and follow the project's centralized package management pattern.

🔒 Security Assessment

Risk Level: ✅ LOW

• Minor patch version update from a trusted, well-maintained verification library
• No security vulnerabilities identified in this version bump
• Package source is legitimate (VerifyTests/Verify GitHub repository)

⚡ Performance Considerations

Impact: ✅ MINIMAL

• Patch version updates typically contain only bug fixes
• No performance regressions expected from verification library updates
• TUnit's custom snapshot testing implementation (TUnit.PublicAPI/Verify.cs, TUnit.Core.SourceGenerator.Tests/Verify.cs) is unaffected

🧪 Test Coverage & Compatibility

Analysis:

• TUnit uses both the external Verify packages AND custom snapshot testing implementations
• External packages used in:
  • TUnit.Assertions.SourceGenerator.Tests
  • TUnit.Core.SourceGenerator.Tests
  • TUnit.PublicAPI
• Custom implementations provide project-specific snapshot testing functionality
• Patch versions maintain backward compatibility

Test Requirements:
According to CLAUDE.md, snapshot tests should be run when dependency changes might affect verification:

dotnet test TUnit.Core.SourceGenerator.Tests
dotnet test TUnit.PublicAPI

🚨 Potential Issues

None identified - This is a routine dependency maintenance update with:

• No breaking changes (patch version)
• No API changes expected
• Minimal risk profile

✅ Recommendation

APPROVE and MERGE - This PR is ready for integration:

1. Safe Update: Patch version with no breaking changes
2. Automated Testing: CI will validate compatibility
3. Low Risk: Minimal impact on TUnit's functionality
4. Good Practice: Keeping dependencies current for security and stability

Note for Maintainers: Consider running the snapshot test suites (TUnit.Core.SourceGenerator.Tests and TUnit.PublicAPI) if any unexpected verification behavior is observed post-merge, though this is unlikely with a patch update.

---