microsoft / microsoft/winget-pkgs
[New Feature]: Wingetbot should skip packages if hash exists and is not for the version being updated
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Description of the new feature/enhancement
When wingetbot detects a hash mismatch for Version A of a package, it will check to be sure that Version B doesn't exist. However, sometimes the new version exists but doesn't exactly match what wingetbot is expecting. Wingetbot should instead check whether or not the new hash exists in any versions of the package rather than relying on strict version comparison.
- See https://github.com/microsoft/winget-pkgs/pull/126100
- See https://github.com/microsoft/winget-pkgs/pull/126062
- See https://github.com/microsoft/winget-pkgs/pull/125873
Proposed technical implementation details (optional)
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
Start by reading the linked pull requests #126100, #126062, and #125873 to understand the hash-mismatch cases and locate the relevant wingetbot behavior. Done means wingetbot checks whether the new hash exists in any version of the package instead of relying on an exact version match.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100