chore(deps): update verify to 31.18.0

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	minor	31.17.0 → 31.18.0
Verify.NUnit	nuget	minor	31.17.0 → 31.18.0
Verify.TUnit	nuget	minor	31.17.0 → 31.18.0

---

Release Notes

VerifyTests/Verify (Verify)

v31.18.0

Compare Source

• #​1739 add BypassComparersForSubsequentOnDifference

---

Configuration

📅 Schedule: (UTC)

• 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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[claude]

Code Review

PR: chore(deps): update verify to 31.18.0

Summary

This is a routine Renovate-generated dependency bump for the Verify snapshot-testing family. The change is minimal and low-risk.

Observations

Interesting diff detail: The Directory.Packages.props diff shows Verify.TUnit going from 31.18.0 → 31.18.0 (same version on both sides). This means Verify.TUnit was already at 31.18.0 before this PR, while Verify and Verify.NUnit are the packages actually being upgraded from 31.17.0. The PR description claims all three packages are being updated, which is slightly misleading — only two packages are actually changing.

This isn't a blocker, but it suggests Verify.TUnit may have been bumped independently in a prior commit while the other two packages were left behind. The end state (all three at 31.18.0) is correct and consistent.

Verdict

The change is correct. All three Verify packages end up at the same 31.18.0 version, which is the right outcome. The new BypassComparersForSubsequentOnDifference feature in 31.18.0 is additive and shouldn't affect existing snapshot tests. ✅ Safe to merge.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}