Default transitive resolver strategy breaks SqlHydra NuGet package
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Paket's ResolverStrategy.Max default and the strategy:min path, then trace how transitive versions are selected for NuGet packages. Done means the project has a resolved decision on the default strategy, with the SqlHydra/SqlKata 2.4.0 case used to verify the outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100