Support additional transitive resolver strategies
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Following on from tweet thread https://twitter.com/BlythMeister/status/1177225164859346945
Whereby some package maintainers (including Microsoft) don't put max version constraints on packages.
Proposed solution is to add 3 new "max" strategies
- max-major - same as max now, max will be depricated
- max-minor - take the max, but don't go up a major version.
- max-patch - take the max, but don't go up a minor version
This means you could use max-minor and take new versions as they are released, but not expose yourself to a breaking transitive dependency.
Therefore helping to resolve issues like this: https://github.com/aspnet/Extensions/issues/2405
This issue it for the discussion of this idea (rather than using Twitter)
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
Review Paket’s existing resolver strategies and the behavior of the current max strategy before deciding how the proposed names and compatibility rules fit together. Done means max-major, max-minor, and max-patch have agreed semantics, the current max behavior is addressed as proposed, and dependency resolution tests cover the version boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100