Skip to content

Default transitive resolver strategy breaks SqlHydra NuGet package #4293

@KaranAhlawat

Description

@KaranAhlawat

The default strategy (ResolverStrategy.Max), picks the highest version of any transitive dependencies it finds.

SqlHydra, in their project, currently rely on SqlKata 2.4.0 as a dependency specified (here). However, when resolving, Paket picks the latest version for SqlKata, which is 4.0.1. This breaks the SqlHydra package, and the end project which has SqlHydra as a direct dep fails to build.

This issue simply goes away if we use the strategy: min.

Opening this issue to discuss reasons for why Max was picked as the default, and if Min should be the default as it aligns with how NuGet resolves packages.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions