microsoft / microsoft/winget-cli
Always record version when creating / updating pin
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
When a pin is added, there is no way to know what version it was added at/for (with the exception of a gating pin). In the case of standard pins, this means there is no way for me to audit if a package upgraded itself outside of winget, since I don’t know what version it was originally pinned to.
Of course, I could use a gating pin with an exact version, but then I wouldn’t be able to upgrade it with an explicit upgrade.
Proposed technical implementation details
No response
Contributor guide
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
The issue names no files, tests, or entry points. Start by reviewing how standard and gating pins are created and updated, including how explicit upgrades work. Done means a standard pin records the version present when it is created or updated while remaining upgradeable explicitly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100