microsoft / microsoft/winget-pkgs
Auto generate manifests for newer versions
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
To support some kind of CI that, based on previously set logic, can auto-generate manifests for newer versions of the packages.
Proposed technical implementation details
A very good example is the Chocolatey Automatic Package Updater Module: https://github.com/majkinetor/au
Based on custom rules, such as scripts for finding newer versions, URLs for downloading them, a CI can run continuously based on a scheduled trigger, and if it finds a newer version, it try to build a new manifest automatically, test it, and submit a PR (or push directly).
So then, we don't need to manually create manifests for every new version of an existing package.
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
No files, tests, or entry points are named. Start by reviewing the proposed scheduled CI workflow, custom version-discovery rules, manifest generation, validation, and PR submission described in the issue. Done would require an agreed design and an end-to-end automated path for detecting, testing, and submitting newer manifests.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100