chore(deps): update dependency verify.nunit to 30.6.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.NUnit	nuget	minor	30.5.0 -> 30.6.0

---

Release Notes

VerifyTests/Verify (Verify.NUnit)

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

---

PR Review: Verify.NUnit Dependency Update

Todo List:

• Read the changed file (Directory.Packages.props)
• Understand repository structure and Verify.NUnit usage
• Check for any test files that might be affected
• Review the dependency update impact
• Provide comprehensive review feedback

---

Review Findings

✅ Code Quality & Best Practices

• The dependency update follows proper .NET central package management practices
• Single line change in Directory.Packages.props is clean and well-structured
• Version bump follows semantic versioning (minor update: 30.5.0 → 30.6.0)

⚠️ Potential Issues

1. Version Inconsistency Risk (Directory.Packages.props:85-86)

<PackageVersion Include="Verify" Version="30.5.0" />
<PackageVersion Include="Verify.NUnit" Version="30.6.0" />

The main Verify package remains at 30.5.0 while Verify.NUnit is updated to 30.6.0. This version mismatch could potentially cause:

• Dependency resolution conflicts
• Runtime compatibility issues
• Inconsistent behavior between verify implementations

Recommendation: Consider updating the main Verify package to 30.6.0 as well to maintain version alignment.

🔍 Analysis of Current Usage

• The codebase implements custom verification logic rather than using Verify.NUnit directly
• Found custom VerifySettingsTask classes in:
  • /TUnit.PublicAPI/Verify.cs:9-171
  • /TUnit.Core.SourceGenerator.Tests/Verify.cs:9-197
• The repository has extensive snapshot testing with 80+ .verified.txt files
• Verify.NUnit package appears unused in actual project references - only declared in central package management

✅ Security

• No security concerns with this minor version update
• Verify library is reputable and widely used in .NET ecosystem

✅ Performance

• Minor version updates in verification libraries typically don't introduce performance regressions
• No performance-critical changes expected

✅ Test Coverage

• Existing snapshot tests will validate that verification behavior remains consistent
• The custom verification implementation should be unaffected by this update

💡 Recommendations

1. Version Alignment: Update the main Verify package to 30.6.0 to match Verify.NUnit
2. Usage Audit: Consider whether Verify.NUnit is actually needed, as the codebase appears to use custom verification logic
3. Testing: Run existing verification tests to ensure no regressions

📋 Summary

This is a low-risk minor dependency update. The primary concern is the version mismatch between Verify (30.5.0) and Verify.NUnit (30.6.0). While the actual impact may be minimal given the custom verification implementation, maintaining version consistency is a best practice.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Verify.NUnit Dependency Update

Todo List:

• Read the changed file (Directory.Packages.props)
• Understand repository structure and Verify.NUnit usage
• Check for any test files that might be affected
• Review the dependency update impact
• Provide comprehensive review feedback

---

Review Findings

✅ Code Quality & Best Practices

• The dependency update follows proper .NET central package management practices
• Single line change in Directory.Packages.props is clean and well-structured
• Version bump follows semantic versioning (minor update: 30.5.0 → 30.6.0)
• Version consistency maintained: Both Verify (line 85) and Verify.NUnit (line 86) are now aligned at version 30.6.0

✅ Potential Issues Assessment

No significant issues identified:

• Version alignment: The main Verify package was already updated to 30.6.0 in PR chore(deps): update dependency verify to 30.6.0 #2815, so both packages are now properly synchronized
• Usage analysis: The codebase implements custom verification logic (VerifySettingsTask in /TUnit.Core.SourceGenerator.Tests/Verify.cs:9-197 and /TUnit.PublicAPI/Verify.cs) rather than using Verify.NUnit directly
• Package references: Only the main Verify package is actually referenced in project files - Verify.NUnit appears to be declared but unused
• No breaking changes: This is a minor version update (30.5.0 → 30.6.0) which should be backward compatible

✅ Security

• No security concerns with this minor version update
• Verify library is a reputable and widely used snapshot testing library in the .NET ecosystem

✅ Performance

• Minor version updates in verification libraries typically have minimal performance impact
• No performance-critical changes expected based on the version bump

✅ Test Coverage

• The repository has extensive snapshot testing with 80+ .verified.txt files
• Existing custom verification implementation will continue to work as expected
• The actual Verify.NUnit package appears unused, so minimal impact on test execution

💡 Recommendations

1. Package cleanup: Consider removing the unused Verify.NUnit package reference from Directory.Packages.props if it's not being used in any project
2. Dependency audit: Review if Verify.NUnit serves a future purpose or can be safely removed to reduce dependency bloat

📋 Summary

This is a low-risk, routine dependency update that maintains proper version alignment with the main Verify package. The change is well-isolated and should not affect the codebase functionality since the project uses custom verification logic rather than the standard Verify.NUnit integration.

Recommendation: ✅ Approve - Safe to merge as-is, with optional cleanup of unused dependencies as a future enhancement.

---