chore(deps): update sourcy to 0.7.9

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Sourcy.DotNet	nuget	patch	0.7.7 -> 0.7.9
Sourcy.Git	nuget	patch	0.7.7 -> 0.7.9

---

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: Sourcy Dependency Update

I've completed my review of this dependency update PR. Here's my comprehensive feedback:

Todo List:

• Read the changed file (Directory.Packages.props)
• Check for Sourcy usage in the codebase to understand impact
• Analyze the version changes (0.7.7 → 0.7.9)
• Provide comprehensive review feedback
• Final assessment and recommendations

Review Feedback

✅ Code Quality & Best Practices

• Excellent dependency management: Using Central Package Management with Directory.Packages.props is a modern best practice
• Proper isolation: Both packages correctly use <PrivateAssets>all</PrivateAssets>, ensuring they're build-time only dependencies
• Clean scope: Packages are only used in test projects and build pipeline, not runtime code

✅ Security Assessment

• Low risk update: Patch version bump (0.7.7 → 0.7.9) indicates bug fixes/minor improvements
• Isolated impact: Private assets configuration prevents these dependencies from affecting consumers
• Trusted source: Sourcy packages are authored by thomhurst (same as this repository owner)

✅ Performance Considerations

• No runtime impact: Both packages are build-time tools that don't affect application performance
• Usage patterns are appropriate:
  • Sourcy.Git.RootDirectory used for test file discovery in /TUnit.Core.SourceGenerator.Tests/Git.cs:5
  • Sourcy.DotNet.Projects.* used for build pipeline project references in /TUnit.Pipeline/Modules/GetPackageProjectsModule.cs:15-21

✅ Potential Bugs/Issues

• Low risk: Patch version updates typically contain only bug fixes
• Backward compatibility: No breaking changes expected for 0.7.x series
• Isolated usage: Limited to test infrastructure, minimizing impact surface

⚠️ Test Coverage Considerations

• Recommendation: Since these packages are used extensively in test infrastructure (23 files), consider running the full test suite to verify compatibility
• Key areas to validate:
  • Source generator tests that rely on Sourcy.Git.RootDirectory
  • Build pipeline modules using Sourcy.DotNet.Projects

Final Assessment

✅ APPROVED - This is a low-risk dependency update with proper isolation and scope. The changes are minimal and well-contained.

Recommendations:

1. Proceed with merge: The update follows best practices and poses minimal risk
2. Monitor CI: Ensure all tests pass, particularly the source generator and pipeline tests
3. Consider automation: The Renovate Bot configuration with automerge is appropriate for patch updates like this

The PR demonstrates excellent dependency management practices and should be safe to merge once CI passes.

---

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: Sourcy Dependency Update

I've completed my review of this dependency update PR. Here's my comprehensive feedback:

Todo List:

• Read the changed file (Directory.Packages.props)
• Check for Sourcy usage in the codebase to understand impact
• Analyze the version changes (0.7.7 → 0.7.9)
• Provide comprehensive review feedback
• Final assessment and recommendations

Review Feedback

✅ Code Quality & Best Practices

• Excellent dependency management: Using Central Package Management with Directory.Packages.props is a modern best practice
• Proper isolation: Both packages correctly use <PrivateAssets>all</PrivateAssets>, ensuring they're build-time only dependencies
• Clean scope: Packages are only used in test projects and build pipeline, not runtime code

✅ Security Assessment

• Low risk update: Patch version bump (0.7.7 → 0.7.9) indicates bug fixes/minor improvements
• Isolated impact: Private assets configuration prevents these dependencies from affecting consumers
• Trusted source: Sourcy packages are authored by thomhurst (same as this repository owner)

✅ Performance Considerations

• No runtime impact: Both packages are build-time tools that don't affect application performance
• Usage patterns are appropriate:
  • Sourcy.Git.RootDirectory used for test file discovery in /TUnit.Core.SourceGenerator.Tests/Git.cs:5
  • Sourcy.DotNet.Projects.* used for build pipeline project references in /TUnit.Pipeline/Modules/GetPackageProjectsModule.cs:15-21

✅ Potential Bugs/Issues

• Low risk: Patch version updates typically contain only bug fixes
• Backward compatibility: No breaking changes expected for 0.7.x series
• Isolated usage: Limited to test infrastructure, minimizing impact surface

⚠️ Test Coverage Considerations

• Recommendation: Since these packages are used extensively in test infrastructure (23 files), consider running the full test suite to verify compatibility
• Key areas to validate:
  • Source generator tests that rely on Sourcy.Git.RootDirectory
  • Build pipeline modules using Sourcy.DotNet.Projects

Final Assessment

✅ APPROVED - This is a low-risk dependency update with proper isolation and scope. The changes are minimal and well-contained.

Recommendations:

1. Proceed with merge: The update follows best practices and poses minimal risk
2. Monitor CI: Ensure all tests pass, particularly the source generator and pipeline tests
3. Consider automation: The Renovate Bot configuration with automerge is appropriate for patch updates like this

The PR demonstrates excellent dependency management practices and should be safe to merge once CI passes.

---