chore(deps): update sourcy to 1.0.3

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Sourcy.DotNet	nuget	patch	1.0.1 → 1.0.3
Sourcy.Git	nuget	patch	1.0.1 → 1.0.3

---

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 Sourcy.DotNet and Sourcy.Git packages from 1.0.1 to 1.0.3 (patch updates).

Critical Issues

None found ✅

TUnit Rules Assessment

• ✅ Dual-Mode: Not applicable (dependency update only)
• ✅ Snapshot Testing: Not applicable (no source generator or API changes)
• ✅ No VSTest: Not applicable (no VSTest dependencies)
• ✅ Performance: Not applicable (dependency update only)
• ✅ AOT Compatible: Not applicable (dependency update only)

Analysis

This is a standard Renovate bot patch update for test-only dependencies. The Sourcy packages are:

• Used only in test projects (TUnit.Core.SourceGenerator.Tests, TUnit.Assertions.SourceGenerator.Tests, etc.)
• Marked with PrivateAssets=all (don't leak to consumers)
• Provide utility methods for finding Git root directory

Patch version updates (1.0.1 → 1.0.3) should contain only bug fixes and are generally safe to merge.

Verdict

✅ APPROVE - No critical issues, safe dependency update

[thomhurst]

Summary

Updates Sourcy.DotNet and Sourcy.Git dependencies from 1.0.1 to 1.0.3.

Critical Issues

None found ✅

Analysis

This is a patch-level dependency update for build-time tools (Sourcy packages). The changes only affect Directory.Packages.props and don't touch any TUnit code, source generators, public APIs, or test execution paths.

No TUnit-specific rules apply to this change:

• ✅ No dual-mode implementation needed (no source gen/engine changes)
• ✅ No snapshot updates needed (no generated output changed)
• ✅ No public API changes
• ✅ No reflection or AOT concerns
• ✅ No VSTest references
• ✅ No performance impact on hot paths

The PR is configured for automerge, which is appropriate for this type of automated dependency update.

Verdict

✅ APPROVE - No critical issues