Skip to content

Conversation

@thomhurst
Copy link
Owner

@thomhurst thomhurst commented Jan 5, 2026

This PR contains the following updates:

Package Type Update Change
Sourcy.DotNet nuget major 0.7.111.0.0
Sourcy.Git nuget major 0.7.111.0.0

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.

Copilot AI review requested due to automatic review settings January 5, 2026 19:56
@thomhurst thomhurst added dependencies Pull requests that update a dependency file MAJOR renovate-bot labels Jan 5, 2026
@thomhurst thomhurst enabled auto-merge (squash) January 5, 2026 19:56
@thomhurst
Copy link
Owner Author

Summary

Updates Sourcy.DotNet and Sourcy.Git from 0.7.9 to 1.0.0 (major version bump).

Critical Issues

None found ✅

Suggestions

None - this is a straightforward dependency update from an automated renovate bot.

Analysis

This PR updates two internal-only build/test dependencies (Sourcy.DotNet and Sourcy.Git) which are used for:

  • Sourcy.Git.RootDirectory - accessing the git root directory in tests
  • Sourcy.DotNet.Projects.* - accessing project file references in the build pipeline

Both packages have PrivateAssets=all, meaning they don't affect TUnit's public API or runtime behavior. The usage is limited to:

  • Test projects (TUnit.Core.SourceGenerator.Tests, TUnit.Engine.Tests, TUnit.RpcTests, TUnit.Assertions.SourceGenerator.Tests)
  • Build pipeline (TUnit.Pipeline)
  • Public API verification tooling (TUnit.PublicAPI)

TUnit Rules Check:

  • ❌ Not a dual-mode change (source-gen/reflection)
  • ❌ No source generator output changes expected
  • ❌ No public API changes
  • ❌ No reflection usage changes
  • ❌ No hot path changes
  • ✅ No VSTest usage introduced

The major version bump should be safe given these are code-generated source providers that simply expose file system references. CI will catch any breaking changes.

Verdict

APPROVE - No critical issues

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates two Sourcy packages from version 0.7.9 to 1.0.0, representing a major version bump. Sourcy.DotNet and Sourcy.Git are build-time source generators that provide compile-time access to project and git repository information. These packages are used exclusively in test projects within the TUnit codebase to access project paths and git root directory information. Since these are marked as PrivateAssets=all, they are not shipped with the library and only affect the build and test processes.

Key Changes

  • Sourcy.DotNet: Updated from 0.7.9 to 1.0.0 - provides compile-time project information access
  • Sourcy.Git: Updated from 0.7.9 to 1.0.0 - provides compile-time git repository information access

@thomhurst
Copy link
Owner Author

Summary

Updates Sourcy.DotNet and Sourcy.Git from 0.7.11 to 1.0.0 (major version bump).

Critical Issues

None found ✅

Analysis

This PR updates two build-time analyzer dependencies (Sourcy.DotNet and Sourcy.Git) to v1.0.0. Both packages are marked with PrivateAssets="all", meaning they're used only during build and don't affect runtime or published artifacts.

TUnit Rules Assessment:

  • ✅ No source generator output changes (Sourcy is a build analyzer, not part of TUnit's source generation)
  • ✅ No public API changes (private build dependencies only)
  • ✅ No VSTest references
  • ✅ No reflection or AOT concerns (build-time only)
  • ✅ No performance impact (build-time analyzers)

Risk Assessment: Low

  • Major version bump could contain breaking changes, but these are build-time analyzers
  • The PR description indicates Renovate has automerge enabled
  • Build success will validate compatibility

Recommendation:
Let CI validate the build. If green, the update is safe to merge. As these are build-time analyzers from the same author (thomhurst), breaking changes are unlikely to cause runtime issues.

Verdict

APPROVE - No critical issues (pending CI validation)

This was referenced Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file MAJOR renovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants