chore(deps): update dependency system.commandline to 2.0.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
System.CommandLine (source)	nuget	patch	2.0.0 -> 2.0.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 this update again.

---

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

---

This PR has been generated by Renovate Bot.

[claude]

Pull Request Review: System.CommandLine 2.0.0 → 2.0.1

Summary

This is an automated dependency update from Renovate Bot that updates System.CommandLine from version 2.0.0 to 2.0.1 (patch version bump).

Code Quality ✅

• Change scope: Minimal and targeted - single line change in Directory.Packages.props
• Type: Patch version update (following semantic versioning)
• Impact: Low risk - patch updates typically contain bug fixes without breaking changes

Dependency Usage Analysis ✅

The System.CommandLine package is used in:

• TUnit.Pipeline/Program.cs (lines 1, 9-22, 51): For CLI argument parsing with Option, RootCommand, and command-line argument handling
• Usage pattern: Standard CLI argument parsing for pipeline categories

The current usage is straightforward and follows System.CommandLine best practices:

• Options defined with proper arity and descriptions
• Root command with action handler
• Parse and invoke pattern (rootCommand.Parse(args).InvokeAsync())

Potential Issues 🔍

None identified - This is a patch release which should only contain:

• Bug fixes
• Performance improvements
• Documentation updates
• No breaking changes expected per semantic versioning

Performance Considerations ✅

• Patch updates often include performance improvements
• No performance regressions expected from CLI parsing library update
• The dependency is only used in the pipeline project, not in hot paths of test execution

Security Concerns ✅

• Official Microsoft package with regular security updates
• Patch updates may include security fixes
• No security vulnerabilities reported with current usage pattern

Test Coverage ✅

• The pipeline project is a build/CI tool, not part of the core testing framework
• CI will validate the build completes successfully
• No additional test coverage needed for dependency updates

Recommendations

✅ APPROVE - This PR is safe to merge:

1. Low Risk: Patch version update from official Microsoft package
2. Limited Scope: Only affects the pipeline build tool, not core TUnit functionality
3. Best Practice: Keeping dependencies up-to-date improves security and stability
4. Automated: Renovate Bot has proper configuration with automerge enabled

Pre-Merge Checklist (Per CLAUDE.md)

• ✅ No source generator changes - N/A
• ✅ No public API changes - N/A
• ✅ No dual-mode implementation needed - N/A
• ✅ No performance-critical code changes - N/A
• ✅ No reflection changes requiring AOT testing - N/A
• ✅ Follows dependency update best practices

Conclusion

This is a routine maintenance update that should be merged once CI passes. The change is minimal, well-scoped, and follows best practices for dependency management.

---

Review generated following TUnit development guidelines from CLAUDE.md

[Copilot]

Pull request overview

This PR updates the System.CommandLine dependency from version 2.0.0 to 2.0.1, a patch version update that should contain only bug fixes and improvements without breaking changes. The dependency is managed centrally through the project's Directory.Packages.props file and is used by the TUnit.Pipeline project for command-line argument parsing.