chore(deps): update xunit to 3.2.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
xunit.v3	nuget	patch	3.2.0 -> 3.2.1
xunit.v3.assert	nuget	patch	3.2.0 -> 3.2.1
xunit.v3.extensibility.core	nuget	patch	3.2.0 -> 3.2.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]

Claude finished @thomhurst's task —— View job

---

PR Review: xunit 3.2.0 → 3.2.1 Update

Todo List:

• Read and analyze the changed file (Directory.Packages.props)
• Review CLAUDE.md for any dependency update guidelines
• Assess code quality and potential issues
• Evaluate security implications
• Check for performance considerations
• Provide comprehensive review feedback

---

✅ Review Summary

This is a low-risk patch update of xunit v3 packages. Here's my comprehensive assessment:

📋 Code Quality & Best Practices

✅ EXCELLENT

• Clean, centralized dependency management using Directory.Packages.props
• Consistent versioning across all xunit.v3 packages (3.2.1)
• No breaking changes (patch version bump)
• Properly maintains separate xunit v2 and v3 packages for compatibility

🛡️ Security Assessment

✅ LOW RISK

• Patch version update from trusted Microsoft/xunit maintainers
• No new dependencies introduced
• Updates are from official xunit repository
• Test framework dependencies have limited attack surface

⚡ Performance Considerations

✅ NEUTRAL TO POSITIVE

• Patch updates typically include bug fixes and performance improvements
• xunit v3 is actively maintained with performance focus
• No architectural changes expected in patch releases
• Should not impact TUnit's core performance (xunit used for internal testing only)

🧪 Test Coverage Impact

✅ MINIMAL IMPACT

• Changes are to test framework dependencies only
• No impact on TUnit's dual-mode execution (source-gen + reflection)
• No public API changes in TUnit itself
• Should not require snapshot test updates

🔍 Specific File Analysis

Directory.Packages.props:94-96

<PackageVersion Include="xunit.v3" Version="3.2.1" />
<PackageVersion Include="xunit.v3.assert" Version="3.2.1" />
<PackageVersion Include="xunit.v3.extensibility.core" Version="3.2.1" />

Analysis:

• All three packages updated consistently
• Maintains version alignment across xunit.v3 ecosystem
• No conflicts with existing xunit v2 packages (lines 91-93)

📊 Repository Context Considerations

Based on CLAUDE.md guidelines, this change:

• ✅ Does NOT require dual-mode implementation (test dependency only)
• ✅ Does NOT change public APIs (no snapshot updates needed)
• ✅ Does NOT affect source generator output
• ✅ Does NOT touch performance-critical paths
• ✅ Does NOT introduce reflection concerns

🚀 Recommendations

1. ✅ APPROVE - This is a safe patch update
2. No manual testing required - Renovate bot handles basic validation
3. CI will validate compatibility - Let existing test suite verify functionality
4. Consider auto-merge - This type of patch update is ideal for automation

🔄 Next Steps

This PR is ready for merge. The automerge configuration should handle this automatically once CI passes. No manual intervention needed unless CI fails unexpectedly.

---

Risk Level: 🟢 LOW
Recommended Action: ✅ APPROVE & MERGE

---