chore(deps): update verify to 31.13.5

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Verify	nuget	patch	31.13.3 → 31.13.5
Verify.NUnit	nuget	patch	31.13.3 → 31.13.5
Verify.TUnit	nuget	patch	31.13.3 → 31.13.5

---

Release Notes

VerifyTests/Verify (Verify)

v31.13.5

Compare Source

v31.13.4

Compare Source

• #​1695 Bump TUnit packages to 1.19.74
• #​1696 DiffEngine 19.1.1

---

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

---

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

---

This PR has been generated by Renovate Bot.

[claude]

Code Review: Dependency Update

This is a straightforward Renovate Bot patch update bumping Verify, Verify.NUnit, and Verify.TUnit from 31.13.3 → 31.13.4.

Assessment: Approved ✓

What changed:

• 3 version bumps in Directory.Packages.props — no logic changes, no new APIs introduced.

Why this is safe:

• Patch-level semver update (no breaking changes expected).
• The upstream 31.13.4 release notes show only: a TUnit package bump to 1.19.74 and a DiffEngine 19.1.1 update — both are internal dependency housekeeping within the Verify ecosystem.
• The project's snapshot (.verified.txt) tests should catch any behavioral regressions from the Verify library update.
• Auto-merge is appropriately enabled for this type of dependency bot PR.

No concerns. This is routine maintenance; the change is minimal, low-risk, and follows the project's established Renovate Bot workflow.

[claude]

Code Review: Dependency Update (Updated)

This PR bumps Verify, Verify.NUnit, and Verify.TUnit from 31.13.3 → 31.13.5 (skipping 31.13.4, so both patch releases are included in one update).

Assessment: Approved ✓

What changed:

• 3 version bumps in Directory.Packages.props — no logic changes, no new APIs.

Why this is safe:

• Patch-level semver update; no breaking changes expected across either 31.13.4 or 31.13.5.
• Upstream release notes for 31.13.4/31.13.5 show only internal dependency housekeeping (TUnit bump to 1.19.74, DiffEngine 19.1.1) — nothing that would affect snapshot behavior.
• The project's .verified.txt snapshot tests serve as a regression net for any behavioral drift in the Verify library.
• Auto-merge is appropriately enabled for this bot-driven patch update.

No concerns. Routine maintenance; minimal, low-risk change.