chore(deps): update dependency nunit to 4.6.0

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
NUnit (source)	4.5.1 → 4.6.0

---

Release Notes

nunit/nunit (NUnit)

v4.6.0: NUnit 4.6.0

Compare Source

See release notes for details.

---

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 this update again.

---

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

---

This PR has been generated by Mend Renovate.

[claude]

Code Review: chore(deps): update dependency NUnit to 4.6.0

Summary

This is an automated Renovate Bot dependency update bumping NUnit from 4.5.1 to 4.6.0 in Directory.Packages.props. Because this repo uses Central Package Management, this single-line change propagates the version bump to all consuming projects automatically.

---

Change Assessment

Scope is correctly minimal. Only the central version pin is changed; no individual .csproj files needed updating. This is the correct pattern for this repo's CPM setup.

Companion packages not updated — worth a quick check. The repo also depends on NUnit.Analyzers and NUnit3TestAdapter. For a minor version bump these companions typically don't require simultaneous updates, but it's worth confirming that the installed versions are compatible with NUnit 4.6.0. Renovate will likely handle any required companion bumps automatically as follow-up PRs.

Low blast radius. NUnit is used in TrxParsingTests.cs purely as the fixture that generates .trx files for parser tests — it is not the primary test framework (that's TUnit). This keeps the risk of this bump well-contained.

Merge confidence is high per Renovate's badge. NUnit 4.5.x → 4.6.0 is a minor semver release with no declared breaking changes.

---

No Issues Found

• No API breakage risk for a minor release.
• No architectural concerns introduced.
• Change is consistent with the existing Renovate-managed dependency strategy.
• Auto-merge is appropriately enabled for a low-risk update like this.

---

✅ Approve and merge. Routine, low-risk dependency bump. No changes needed.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	✅ 0 (≤ 20 complexity)

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.}