microsoft / microsoft/winget-pkgs

[New Feature]: wingetbot should remove volatile fields when automatically upgrading packages

Open
#96,092 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Bots Area-Validation-Pipeline 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

Several fields are more likely than not to change between versions. wingetbot currently leaves these fields as-is when upgrading a package

  • Release Notes
  • Release Notes URL
  • Release Date
Proposed technical implementation details (optional)

Update or remove the fields if present

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating wingetbot's automatic package-upgrade logic and the manifest handling for Release Notes, Release Notes URL, and Release Date. Check how upgrades currently preserve these fields. Done means those fields are updated or removed when present during automatic upgrades, with the relevant verification completed.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.