chore(deps): update dependency verify.tool to v0.7.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
verify.tool	nuget	minor	0.6.0 -> 0.7.0

---

Release Notes

patriksvensson/verify.terminal (verify.tool)

v0.7.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

---

Pull Request Review: verify.tool v0.7.0 Update

Review Tasks

• Read and analyze the changed file
• Check for breaking changes in release notes
• Search for verify.tool usage in codebase
• Assess security implications
• Check test coverage and documentation needs
• Provide comprehensive review feedback

Review Summary ✅

This is a low-risk, straightforward dependency update that should be approved.

Analysis

What Changed

• File: .config/dotnet-tools.json
• Change: verify.tool version updated from 0.6.0 to 0.7.0
• Type: Minor version update of a .NET global tool

Tool Purpose & Usage

The verify.tool is a command-line utility for the Verify snapshot testing framework. In this codebase:

• Used by: Snapshot testing in TUnit.PublicAPI, TUnit.Core.SourceGenerator.Tests, and TUnit.Assertions.SourceGenerator.Tests
• Function: Provides dotnet-verify command for managing .received.txt and .verified.txt files
• Integration: Works with Verify and Verify.TUnit NuGet packages already used in the project

Security Assessment ✅

• Tool Source: patriksvensson/verify.terminal - reputable maintainer
• Scope: Limited to snapshot file management operations
• Risk Level: Very Low - utility tool with no network operations or sensitive data access

Breaking Changes Assessment ✅

• Release Notes: No breaking changes mentioned in the 0.6.0 → 0.7.0 transition
• Compatibility: Minor version update follows semantic versioning
• Impact: No code changes required

Test Coverage & Performance ✅

• Tests: No additional tests needed - this is a development tool dependency
• Performance: No impact on runtime performance (development-time tool only)
• CI/CD: Should work seamlessly with existing snapshot test workflows

Code Quality ✅

• Configuration: Tool correctly configured with rollForward: true
• Consistency: Follows established patterns in the dotnet-tools.json file
• Dependencies: No conflicts with existing tool versions

Recommendations

1. ✅ Approve and merge - This is a safe, routine dependency update
2. ✅ Automerge enabled - Appropriate for this type of change
3. ✅ No additional actions required - Tool update is self-contained

Final Assessment

Code Quality: Excellent
Security: No concerns
Performance: No impact
Best Practices: Follows conventional dependency management
Test Coverage: Adequate (no additional coverage needed)

This PR maintains the project's commitment to keeping development tools current while posing minimal risk to the codebase.

---