microsoft / microsoft/winget-cli
Separate "PackageVersion" from "Marketing Version"
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
Currently, there is the concept of two different versions
- The Marketing Version
- The DisplayVersion
Guidance has been to use PackageVersion as the marketing version and using the AppsAndFeaturesEntries to define the DisplayVersion when it differs from the marketing version.
I propose adding a new manifest field MarketingVersion - which would allow the version to be arbitrary and duplicative while still retaining a semantic version for PackageVersion
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
Start by tracing how manifest fields PackageVersion, DisplayVersion, and AppsAndFeaturesEntries are currently interpreted in the WinGet CLI. Define the manifest behavior for a new MarketingVersion field, including arbitrary or duplicate marketing values while PackageVersion remains semantic, and verify the related version-display paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100