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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify.NUnit	nuget	minor	31.0.5 -> 31.1.0

---

Release Notes

VerifyTests/Verify (Verify.NUnit)

v31.1.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 changed file to understand the update
• Analyze Verify.NUnit library usage in codebase
• Check for any breaking changes or considerations
• Provide comprehensive review feedback

---

Code Quality & Best Practices ✅

The change follows proper centralized package management practices using Directory.Packages.props. The version bump from 31.0.5 to 31.1.0 is a minor release, indicating backward compatibility.

Potential Issues 🔍

Version Misalignment Detected: After analyzing the codebase, I found:

• Verify (base): 31.0.5
• Verify.NUnit: 31.1.0 (this update)
• Verify.TUnit: 31.0.5

Key Finding: Verify.NUnit is defined in central package management but not actually referenced by any .csproj files in the codebase. The project exclusively uses Verify.TUnit (see TUnit.PublicAPI/TUnit.PublicAPI.csproj:17).

Performance Considerations ⚡

No performance impact - the package is not actively used in the codebase.

Security Concerns 🔒

No security concerns for this minor version bump from a reputable library.

Test Coverage 🧪

Not applicable - package is unused. However, the project has comprehensive snapshot testing via Verify.TUnit.

Recommendations 📋

1. Consider removing unused dependency: Since Verify.NUnit is not referenced anywhere, consider removing it from Directory.Packages.props to reduce dependency bloat
2. Version alignment: If keeping for future use, consider aligning all Verify packages to the same version (31.1.0) for consistency
3. Documentation: If this package serves a specific purpose (e.g., compatibility testing), document why it's maintained

Verdict 🎯

Safe to merge - This is a low-risk dependency update of an unused package. The change itself is fine, but the unused dependency raises questions about necessity.