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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.NUnit	nuget	minor	30.12.0 -> 30.13.0

---

Release Notes

VerifyTests/Verify (Verify.NUnit)

v30.13.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: Dependency Update - Verify.NUnit 30.12.0 → 30.13.0

Summary

✅ Approval Recommended - This is a safe minor version update with no breaking changes expected.

Code Quality & Analysis

✅ Positive Findings:

• Clean, automated update: Standard Renovate dependency bump from 30.12.0 → 30.13.0
• Minor version change: Following semantic versioning, no breaking changes expected
• Consistent with codebase standards: Uses centralized package management via Directory.Packages.props (line 86)

⚠️ Critical Issue Identified:

Verify.NUnit appears to be an orphaned dependency!

Evidence:

• Declared in Directory.Packages.props:86 but no .csproj files reference Verify.NUnit
• Only projects use Verify (30.12.0) and Verify.TUnit (30.12.0) packages
• Recent commit history shows this dependency was added via Renovate PR chore(deps): update dependency verify.nunit to 30.12.0 #3092 (Sept 11, 2025)
• No actual usage found in the codebase despite extensive search

Security & Performance Considerations

✅ Security:

• No security concerns with this minor version update
• Dependency comes from trusted source (VerifyTests organization)

✅ Performance:

• Zero performance impact - the package isn't actually used anywhere in the codebase
• No allocations or runtime implications since it's unused

Test Coverage Implications

⚠️ Potentially Insufficient:

• Since Verify.NUnit is unused, this update has no test coverage implications
• However, the presence of an unused dependency suggests potential oversight in dependency management

Recommendations

🔧 Action Required:

1. Consider removing Verify.NUnit entirely from Directory.Packages.props since it's not used
2. If keeping for future use: Document the intended purpose
3. Update Verify.TUnit version from 30.12.0 → 30.13.0 to maintain version consistency across Verify packages

📋 Follow-up Tasks:

• Audit other potentially unused dependencies
• Consider adding dependency usage validation to CI pipeline
• Align Verify package versions (currently Verify.NUnit=30.13.0, Verify=30.12.0, Verify.TUnit=30.12.0)

✅ Specific to TUnit Guidelines:

• Follows centralized package management pattern ✓
• No impact on source generator or reflection modes ✓
• No snapshot test updates needed ✓
• No breaking changes ✓

Verdict

LGTM - The update itself is safe, but the project would benefit from cleaning up this unused dependency.

---