Skip to content

Update dependency ModularPipelines.Git to v3 - autoclosed #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Nice3point wants to merge 1 commit into from
Closed

Update dependency ModularPipelines.Git to v3 - autoclosed #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Directory.Packages.props
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@
<!-- Build Automation -->
<PackageVersion Include="Sourcy.DotNet" Version="0.7.9"/>
<PackageVersion Include="ModularPipelines" Version="2.48.30"/>
<PackageVersion Include="ModularPipelines.Git" Version="2.48.30"/>
<PackageVersion Include="ModularPipelines.Git" Version="3.0.1"/>
Copy link

Copilot AI Jan 17, 2026

Choose a reason for hiding this comment

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

This update creates a version compatibility issue. ModularPipelines.Git is being updated to v3.0.1, but the other ModularPipelines packages (ModularPipelines, ModularPipelines.GitHub, and ModularPipelines.DotNet) remain on v2.48.30.

According to the v3.0.0 release notes, this is a major version with significant breaking changes and API redesigns. Mixing v2 and v3 packages may cause runtime incompatibilities, type conflicts, or unexpected behavior.

All ModularPipelines packages should be updated together to maintain compatibility, or all should remain on v2 until the codebase is ready to migrate to v3.

Suggested change
<PackageVersion Include="ModularPipelines.Git" Version="3.0.1"/>
<PackageVersion Include="ModularPipelines.Git" Version="2.48.30"/>

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Jan 17, 2026

Choose a reason for hiding this comment

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

The codebase still uses the ModularPipelines v2 API patterns, which are incompatible with v3. According to the v3.0.0 release notes, the following breaking changes affect this codebase:

  1. Entry point: The code uses PipelineHostBuilder.Create() (v2) but v3 requires Pipeline.CreateBuilder(args)
  2. Module signatures: All modules use ExecuteAsync(IPipelineContext context, ...) but v3 changed this to use IModuleContext
  3. Result access: The code uses GetModule<T>() on module instances, but v3 requires calling it on the context: context.GetModule<T>()
  4. Lifecycle methods: The code uses OnAfterExecute(IPipelineContext context) which has been replaced with a different pattern in v3

Before updating to ModularPipelines.Git v3.0.1, the entire codebase needs to be migrated to the v3 API. This affects Program.cs and all module files in the build/ directory.

Suggested change
<PackageVersion Include="ModularPipelines.Git" Version="3.0.1"/>
<PackageVersion Include="ModularPipelines.Git" Version="2.48.30"/>

Copilot uses AI. Check for mistakes.
<PackageVersion Include="ModularPipelines.GitHub" Version="2.48.30"/>
<PackageVersion Include="ModularPipelines.DotNet" Version="2.48.30"/>
<PackageVersion Include="Microsoft.Extensions.Options.DataAnnotations" Version="10.0.1"/>
Expand Down
Loading