chore(deps): update dependency modularpipelines.git to 2.48.1

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
ModularPipelines.Git	nuget	minor	2.47.8 -> 2.48.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]

Claude finished @thomhurst's task —— View job

---

Reviewing Dependency Update: ModularPipelines.Git 2.47.8 → 2.48.1

Todo List:

• Read the changed file to understand the exact dependency update
• Analyze the dependency version change for potential issues
• Check for any security concerns or breaking changes
• Review impact on test coverage and build process
• Provide comprehensive review feedback

---

Code Quality and Best Practices ✅

The dependency update is straightforward and follows best practices:

• Uses centralized package management via Directory.Packages.props
• Only updates the version number from 2.47.8 to 2.48.1
• No breaking changes expected for a minor version update

Potential Issues ⚠️

Version Inconsistency Detected:
I noticed that while ModularPipelines.Git is being updated to 2.48.1, the related packages remain at older versions:

• ModularPipelines.DotNet: 2.47.8 (Directory.Packages.props:48)
• ModularPipelines.Git: 2.48.1 (Directory.Packages.props:49) ← Updated
• ModularPipelines.GitHub: 2.47.8 (Directory.Packages.props:50)

Recommendation: Consider updating all ModularPipelines.* packages to the same version to maintain consistency and avoid potential compatibility issues.

Performance Considerations ✅

• Minor version updates typically don't introduce performance regressions
• ModularPipelines.Git is used in the build pipeline (TUnit.Pipeline project), not in runtime code
• No performance impact expected on the main TUnit library

Security Concerns ✅

• Minor version updates from trusted packages (ModularPipelines) are generally safe
• No known security vulnerabilities in the version range
• The package is only used in build/CI pipeline, not in production code

Test Coverage 📋

Analysis:

• ModularPipelines.Git is used extensively in /TUnit.Pipeline/ modules for git operations:
  • Version generation (GenerateVersionModule.cs:13)
  • Commit operations (CommitFilesModule.cs)
  • Tag creation (PushVersionTagModule.cs)
  • Release management (CreateReleaseModule.cs)

Testing Recommendations:

1. Run the full CI pipeline to ensure git operations still work correctly
2. Test version generation functionality specifically
3. Verify that git tagging and release creation still function

Overall Assessment

✅ SAFE TO MERGE with the following recommendations:

1. Address version inconsistency: Consider updating ModularPipelines.DotNet and ModularPipelines.GitHub to 2.48.1 as well
2. Test pipeline functionality: Ensure the build pipeline runs successfully after this update
3. Monitor for issues: Watch for any git-related pipeline failures after deployment

The update itself is low-risk since it's a minor version bump for a build-time dependency, but the version mismatch with related packages should be addressed for consistency.

---