microsoft / microsoft/winget-cli
Remove support for Singleton manifests
Open
Nobody has claimed this yet.
Issue-Feature
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
Creating this issue as I haven’t seen one officially made yet. I know it has been discussed, but not seeing anything formally tracking it.
This would be a potentially breaking change.
As tools to create manifests are now to the point that multimanifests are easy to make, the singleton manifest may be phased out.
Proposed technical implementation details
- Have a warning in the community repo for a period, notifying users that singletons will not be supported in the future
- Transition to a pipeline failure in the community repo
- Eventually fully remove support for singletons in future manifest versions
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 reviewing how the community repo currently validates singleton manifests and how manifest versions are handled. Trace the proposed warning, pipeline failure, and eventual removal stages, then define the compatibility and migration checks needed for each stage.
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
- 25/100