microsoft / microsoft/winget-pkgs
Trigger manifest validation/update on client reported hash mismatch
Open
Nobody has claimed this yet.
Issue-Feature
- 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
This feature represents the back-end services work to support https://github.com/microsoft/winget-cli/issues/870 Provide mechanism to report SHA256 mismatch represents the client work to provide notification for hash mismatches.
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 client issue #870 and tracing how the backend services handle package manifests and client-reported SHA256 mismatches. Done means defining and implementing the service behavior that triggers manifest validation or an update after a reported hash mismatch, with coverage for that workflow.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100