chore(deps): update dependency humanizer to v3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Humanizer	nuget	major	2.14.1 -> 3.0.1

---

Release Notes

Humanizr/Humanizer (Humanizer)

v3.0.1

Changes:

• #​1651: Renormalize line endings
• #​1648: Extract duplicated regex patterns into constants across conditional compilation regions
• #​1649: Delete dotnet.config
• #​1647: move to net10 stable
• #​1641: Add analyzer tests to CI and fix test failures

This list of changes was auto generated.

---

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

---

Code Review: Humanizer v3 Dependency Update

Todo List:

• Read changed file (Directory.Packages.props)
• Read repository guidelines (CLAUDE.md)
• Search codebase for Humanizer usage
• Analyze breaking changes in Humanizer v3
• Review security and performance implications
• Provide comprehensive feedback

Analysis Summary:

Code Quality & Best Practices ✅

POSITIVE: The change follows proper dependency management patterns:

• Uses centralized package management (Directory.Packages.props)
• Single line change from 2.14.1 to 3.0.1
• Clean, minimal modification

Usage Analysis 🔍

LOW RISK: Minimal usage found in codebase:

• Only usage: HumanizerDisplayNameTests.cs:21 - calls TestName.Humanize() for test display names
• Impact scope: Limited to test display formatting only
• Projects affected: TUnit.TestProject and Playground (both test/development projects)

Breaking Changes Assessment ⚠️

MAJOR VERSION UPGRADE (2.x → 3.x) considerations:

• Potential issues: Major version bumps typically introduce breaking changes
• Risk level: LOW due to minimal usage (single .Humanize() method call)
• Mitigation: The basic .Humanize() extension method is core functionality unlikely to change

Security Considerations ✅

NO CONCERNS:

• Humanizer is a well-established library for text processing
• No security vulnerabilities introduced by this update
• Library used only for display name formatting, not security-critical operations

Performance Considerations ✅

POTENTIAL IMPROVEMENT:

• Humanizer v3 likely includes performance improvements
• Usage limited to test display names (non-critical path)
• No performance regression expected

Test Coverage Assessment ⚠️

RECOMMENDATION:

• The existing HumanizerDisplayNameTests should verify compatibility
• Test covers the exact usage pattern (This_test_name_is_formatted_nicely → display name formatting)
• Action needed: Run tests to verify no behavioral changes in formatted output

Repository-Specific Considerations 🎯

Based on CLAUDE.md guidelines:

• ✅ No dual-mode implementation required (library dependency only)
• ✅ No source generator changes involved
• ✅ No public API changes in TUnit
• ⚠️ Testing needed: Per Rule 1, should verify both execution modes work with new version

Recommendations:

1. APPROVE - Low risk change with minimal impact
2. Verify - Ensure HumanizerDisplayNameTests passes with new version
3. Monitor - Check CI results for any unexpected test failures
4. Consider - Review release notes of Humanizer v3 for any relevant changes

Conclusion:

This is a low-risk dependency update with minimal codebase impact. The upgrade should be safe given the limited usage scope and the stability of the core .Humanize() API.

---