Support pinning with SemVer range
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
I would like to be able to pin a package with a SemVer range.
This would be useful particularly when you want to not upgrade to a newer major version but do upgrade for any new minor versions.
For example if I was using Beyond Compare, but only had a license for v3 then I would not want to take any newer v4.x versions, but if they released a new 3.x then I would want that.
Something like:
`choco pin add -n=beyondcompare -version="[3.0,4,0)"`
### Related
[Clickup task](https://app.clickup.com/t/20540031/PROJ-321).
Contributor guide
Research direction
Start by reviewing the existing `choco pin add` command and the project's current version-handling behavior. Use the SemVer range example in the issue as the acceptance case, and confirm how the ClickUp task relates before beginning; done means pinning can accept a range that permits minor updates while excluding newer major versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100