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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.TUnit	nuget	minor	30.13.0 -> 30.15.0

---

Release Notes

VerifyTests/Verify (Verify.TUnit)

v30.15.0

Compare Source

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

---

Code Review: Dependency Update - Verify.TUnit 30.15.0

Todo List:

• Read and analyze the changed file
• Check Verify.TUnit usage in codebase
• Review release notes and potential impact
• Provide comprehensive review feedback
• Check if tests need to be run per CLAUDE.md guidelines

Code Quality and Best Practices ✅

Change Analysis:

• File: Directory.Packages.props:90
• Change: Verify.TUnit version bump from 30.13.0 → 30.15.0
• Type: Minor version update (2 patch versions)

This is a clean, centralized package management update following .NET best practices with ManagePackageVersionsCentrally.

Potential Issues and Concerns ⚠️

Version Inconsistency:

• Verify.TUnit is being updated to 30.15.0
• Verify (base package) remains at 30.14.0 (line 85)
• Verify.NUnit remains at 30.13.0 (line 86)

Recommendation: Consider updating all Verify packages to the same version to maintain consistency and avoid potential compatibility issues.

Impact on TUnit Codebase 🔍

Usage Locations:

• Used in TUnit.Core.SourceGenerator.Tests (snapshot testing)
• Used in TUnit.Assertions.SourceGenerator.Tests
• Used in TUnit.PublicAPI (likely for API verification)

Critical per CLAUDE.md guidelines: This update affects packages used for snapshot testing, which means you should run:

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

Performance Considerations ✅

Minor version updates in Verify.TUnit typically focus on bug fixes and minor improvements. No performance regressions expected for this type of update.

Security Concerns ✅

• Renovate Bot dependency updates are generally secure
• Minor version bumps in well-maintained packages like Verify.TUnit pose minimal security risk
• No breaking changes expected in patch releases

Test Coverage Requirements 🧪

According to CLAUDE.md:

Run snapshot tests when changing source generator output or public APIs

Since Verify.TUnit is used for snapshot testing in source generator tests, you must run:

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

If snapshots change, accept them by renaming .received.txt → .verified.txt files.

Recommendations 📋

1. Update related packages for consistency:

   <PackageVersion Include="Verify" Version="30.15.0" />
   <PackageVersion Include="Verify.NUnit" Version="30.15.0" />

2. Run the required tests before merging:

   • Source generator snapshot tests
   • Public API tests

3. Monitor for snapshot changes and accept if they represent intended behavior

Overall Assessment ✅

This is a low-risk, routine dependency update. The change is well-isolated, follows best practices, and should be safe to merge after running the recommended tests.

Approval Status: ✅ Safe to merge with recommendations addressed

---

[claude]

Claude finished @thomhurst's task —— View job

---

Code Review: Dependency Update - Verify.TUnit 30.15.0

Todo List:

• Read and analyze the changed file
• Check Verify.TUnit usage patterns in codebase
• Review version consistency with related Verify packages
• Check CLAUDE.md requirements for snapshot testing
• Provide comprehensive review feedback

### Code Quality and Best Practices ✅

Change Analysis:

• File: Directory.Packages.props:90
• Change: Verify.TUnit version bump from 30.13.0 → 30.15.0
• Type: Minor version update (2 patch versions)

This follows .NET best practices using centralized package management with ManagePackageVersionsCentrally.

### Potential Issues and Concerns ⚠️

Version Inconsistency Detected:

• Verify.TUnit updating to 30.15.0 ✅
• Verify.NUnit already at 30.15.0 ✅
• Verify (base package) remains at 30.14.0 ❌

Recommendation: Update the base Verify package to 30.15.0 for consistency:

<PackageVersion Include="Verify" Version="30.15.0" />

### Performance Considerations ✅

Minor version updates in Verify.TUnit typically include bug fixes and minor improvements. No performance regressions expected for this maintenance update.

### Security Concerns ✅

• Renovate Bot dependency updates are generally secure
• Minor version bumps in well-maintained packages like Verify.TUnit pose minimal security risk
• No breaking changes expected in patch/minor releases

### Test Coverage Requirements 🧪

Critical per CLAUDE.md guidelines: Since Verify.TUnit is used for snapshot testing, you must run these commands before merging:

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

Usage locations identified:

• TUnit.Core.SourceGenerator.Tests - Source generator snapshot verification
• TUnit.PublicAPI - Public API surface verification
• TUnit.Assertions.SourceGenerator.Tests - Assertions generator testing

If snapshots change, they must be accepted by renaming .received.txt → .verified.txt files and committed.

### Overall Assessment ✅

This is a low-risk, routine dependency update. The change follows best practices and should be safe to merge after addressing the version consistency issue and running the required tests.

Issues to Address:

1. ⚠️ Update base Verify package to 30.15.0 for consistency
2. ✅ Run required snapshot tests per CLAUDE.md guidelines

Approval Status: Safe to merge with recommendations addressed

---

[claude]

Claude finished @thomhurst's task —— View job

---

Code Review: Dependency Update - Verify.TUnit 30.15.0

Todo List:

• Read and analyze the changed file (Directory.Packages.props)
• Check Verify.TUnit usage patterns in codebase
• Review version consistency with other Verify packages
• Check CLAUDE.md requirements for dependency updates
• Provide comprehensive review feedback

---

Code Quality and Best Practices ✅

Change Analysis:

• File: Directory.Packages.props:90
• Change: Verify.TUnit version bump from 30.13.0 → 30.15.0
• Type: Minor version update (2 patch versions)

This follows .NET best practices using centralized package management with ManagePackageVersionsCentrally=true. The change is clean and properly isolated.

Potential Issues and Concerns ✅

Version Consistency - EXCELLENT:
All Verify packages are now properly aligned:

• Verify at 30.15.0 (line 85) ✅
• Verify.NUnit at 30.15.0 (line 86) ✅
• Verify.TUnit at 30.15.0 (line 90) ✅

This resolves the version inconsistency that was present in previous iterations where packages were at different versions.

Performance Considerations ✅

Minor version updates in Verify.TUnit typically include bug fixes and minor improvements. Given that this is a testing-only dependency used for snapshot verification, there should be no runtime performance impact on TUnit itself.

Security Concerns ✅

• Renovate Bot dependency updates are generally secure and well-vetted
• Minor version bumps in well-maintained packages like Verify.TUnit pose minimal security risk
• No breaking changes expected in patch/minor releases
• Package source is trusted (VerifyTests organization)

Test Coverage Requirements ⚠️ CRITICAL

Per CLAUDE.md guidelines: Since Verify.TUnit is used for snapshot testing, you MUST run these commands before merging:

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

Usage locations identified:

• TUnit.Core.SourceGenerator.Tests - Source generator snapshot verification
• TUnit.PublicAPI - Public API surface verification
• TUnit.Assertions.SourceGenerator.Tests - Assertions generator testing

CLAUDE.md Rule #2 states:

Run snapshot tests when changing:

• Source generator output: dotnet test TUnit.Core.SourceGenerator.Tests
• Public APIs: dotnet test TUnit.PublicAPI

If snapshots change: Accept them by renaming .received.txt → .verified.txt files and commit the changes.

Impact Assessment ✅

This dependency update affects snapshot testing infrastructure only and should have:

• Zero impact on TUnit runtime performance
• Zero impact on TUnit public APIs
• Potential minor improvements in Verify.TUnit testing capabilities
• No breaking changes for existing test suite

Recommendations 📋

1. ✅ Version consistency achieved - All Verify packages properly aligned at 30.15.0
2. ⚠️ Run required tests before merging:

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

3. ✅ Monitor for snapshot changes and accept if they represent intended behavior

Overall Assessment ✅

This is a low-risk, routine dependency update that follows best practices and maintains proper version consistency across all Verify packages. The change is well-isolated and should be safe to merge after running the mandatory snapshot tests.

Critical Action Required: Run the snapshot tests per CLAUDE.md requirements before merging.

Approval Status: ✅ Safe to merge after running required tests

---