chore(deps): update dependency verify.tunit to 30.18.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.TUnit	nuget	minor	30.17.0 -> 30.18.0

---

Release Notes

VerifyTests/Verify (Verify.TUnit)

v30.18.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

Reviewing this dependency update PR for verify.tunit 30.17.0 → 30.18.0.

Todo List:

• Read the changed file to understand the update
• Examine project structure to understand Verify.TUnit usage
• Check for any breaking changes or compatibility issues
• Assess impact on test coverage and functionality
• Provide comprehensive review feedback

---

Review Feedback

✅ Overall Assessment: APPROVED

This is a straightforward minor version update from Verify.TUnit 30.17.0 to 30.18.0 that looks safe to merge.

Code Quality & Best Practices

• ✅ Proper centralized package management: Uses Directory.Packages.props for version management
• ✅ Consistent versioning: Base Verify package was already updated to 30.18.0 in commit d019252, this aligns the TUnit extension
• ✅ Automated dependency management: Renovate is properly configured with automerge

Compatibility & Breaking Changes

• ✅ Minor version update: 30.17.0 → 30.18.0 follows semantic versioning (patch/minor changes only)
• ✅ No breaking changes expected: Minor version bumps in the Verify ecosystem typically contain only bug fixes and non-breaking features
• ✅ Custom verification implementation: Project uses custom VerifyTUnit wrapper in /TUnit.Core.SourceGenerator.Tests/Verify.cs:194-197, which should remain compatible

Test Coverage & Usage

• ✅ Snapshot testing: Verify.TUnit is used for snapshot testing in source generator tests, which is critical for TUnit's dual execution mode validation
• ✅ Multiple test projects: Used across:
  • TUnit.Core.SourceGenerator.Tests (source generator snapshot tests)
  • TUnit.Assertions.SourceGenerator.Tests (assertion generator tests)
  • TUnit.PublicAPI (API surface verification)

Performance Considerations

• ✅ No performance impact: Verify.TUnit is a testing-only dependency that doesn't affect runtime performance
• ✅ Build-time only: Used exclusively for test verification, not in production code paths

Security Concerns

• ✅ No security risks: Standard dependency update from a trusted package (VerifyTests ecosystem)
• ✅ Test-only scope: Limited to test projects, not exposed in production surface

Recommendations

1. ✅ Proceed with merge: This is a safe update that maintains compatibility
2. ✅ Automerge enabled: Appropriate for this type of routine maintenance update
3. ✅ Monitor CI: Let the existing test suite validate the update (snapshot tests in TUnit.Core.SourceGenerator.Tests will catch any issues)

---

Summary: This dependency update is well-structured, safe, and follows TUnit's development practices. The project's comprehensive snapshot testing will validate compatibility automatically.