chore(deps): update modularpipelines to 3.0.124

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
ModularPipelines.DotNet	nuget	patch	3.0.1 → 3.0.124
ModularPipelines.Git	nuget	patch	3.0.1 → 3.0.124
ModularPipelines.GitHub	nuget	patch	3.0.1 → 3.0.124

---

Release Notes

thomhurst/ModularPipelines (ModularPipelines.DotNet)

v3.0.124: 3.0.124

What's Changed

• fix: resolve console output glitches with progress display by @​thomhurst in #​2193

Full Changelog: thomhurst/ModularPipelines@v3.0.123...v3.0.124

v3.0.86: 3.0.86

What's Changed

• [Automated] Update pnpm CLI Options by @​thomhurst in #​2181
• [Automated] Update grype CLI Options by @​thomhurst in #​2187
• [Automated] Update vault CLI Options by @​thomhurst in #​2189

Full Changelog: thomhurst/ModularPipelines@v3.0.84...v3.0.86

---

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.

[thomhurst]

Summary

Updates ModularPipelines build dependencies from 3.0.1 to 3.0.86.

Critical Issues

None found ✅

Suggestions

None - this is a straightforward dependency update that doesn't touch any TUnit core code or public APIs.

Verdict

✅ APPROVE - No critical issues

This Renovate bot update only modifies Directory.Packages.props to bump ModularPipelines build tool versions. No TUnit-specific rules apply since this doesn't affect test discovery, source generation, public APIs, or runtime behavior.

[thomhurst]

Summary

Updates ModularPipelines build dependencies from 3.0.1 to 3.0.86 (patch version bump).

Critical Issues

None found ✅

This is a straightforward dependency update for build pipeline packages. No runtime code is affected, and no TUnit-specific rules apply (no source generator, public API, reflection, or hot path changes).

Verdict

✅ APPROVE - No critical issues

Safe to merge. The patch version bump should maintain backward compatibility.

[thomhurst]

Summary

This PR updates ModularPipelines dependencies from version 3.0.1 to 3.0.86 (DotNet, Git, and GitHub packages).

Critical Issues

None found ✅

Analysis

Files Changed:

• Directory.Packages.props - Only dependency version updates

TUnit Rules Assessment:

❌ Dual-Mode: Not applicable (no changes to TUnit.Core.SourceGenerator or TUnit.Engine)

❌ Snapshot Testing: Not applicable (no source generator output or public API changes)

❌ VSTest: Not applicable (no test platform dependencies changed)

❌ Performance: Not applicable (build-time dependencies only, not runtime)

❌ AOT Compatibility: Not applicable (no code changes)

Risk Assessment:

• Low Risk: ModularPipelines packages are build/pipeline tooling dependencies
• Minor version jump: While the patch number jumped significantly (3.0.1 → 3.0.86), these are still in the same minor version (3.0.x)
• No code changes: Pure dependency update with no source code modifications
• Automated PR: Generated by Renovate Bot with automerge enabled, suggesting routine maintenance

Verdict

✅ APPROVE - No critical issues

This is a straightforward dependency update that doesn't affect TUnit's core functionality, test execution, or public APIs. The changes are limited to build tooling packages and don't trigger any of TUnit's critical rules.

[thomhurst]

Summary

Updates ModularPipelines.DotNet, ModularPipelines.Git, and ModularPipelines.GitHub from version 3.0.1 to 3.0.124.

Critical Issues

None found ✅

This is a straightforward dependency update that:

• Only modifies Directory.Packages.props (build configuration)
• Updates build/pipeline dependencies (not runtime or testing framework dependencies)
• Does not touch any TUnit source code, source generators, or test discovery logic
• Does not modify public APIs
• Does not introduce any security vulnerabilities

The changes don't trigger any of TUnit's critical rules:

• ❌ No source generator changes
• ❌ No test discovery changes
• ❌ No public API changes
• ❌ No reflection usage
• ❌ No hot path changes
• ❌ No VSTest references

Suggestions

None - this is a clean dependency update.

Verdict

✅ APPROVE - No critical issues. This is a routine dependency update for build pipeline tooling that doesn't affect TUnit's core functionality, APIs, or testing behavior.