Closed Dragon1573 closed 3 months ago
karliss
commented
3 months ago The moderators of microsoft/winget-pkgs recommend authors or publishers automate their submit process,
Sounds reasonable, do you have any links to docs or discussions with winget-pkgs moderators mentioning that this is the the recommended way for maintaining winget manifests?
Dragon1573
commented
3 months ago Sorry, it's my fault. 😥 I can't find such kinds of documentations or discussions posted by Microsoft.
But I found several manifests (such as Oh My Posh) are directly maintained by the package author. They use GitHub Actions like WinGet Releaser, or implement the automation using shell scripts with YamlCreate.ps1, wingetcreate.exe or komac.exe. Most of their pull requests can be merged no more than 24 hours.
For manual maintainence, this may take much longer. Community contributors and volunteers might not notice about the new release. The manifest will keep outdated until somebody open an issue complaining about it, and other create a pull request for manually update it.
@denelon Sorry to ping you here. Is there any official guide for package authors and publishers, which help them automate the manifest maintainence?
Is this feature request related to a problem?
NO. This feature is not for
cutterexecutables.Currently, this application is submitted to microsoft/winget-pkgs as
Rizin.Cutterby contributors or volunteers. The manifest is manually updated at the moment, so some of the users complaining about the outdated manifests.The moderators of microsoft/winget-pkgs recommend authors or publishers automate their submit process, so a newer manifests can immediately noticed and submitted to the repository once the package is released.
Targets we want to achieve
Configure a GitHub Workflow, automatically invoked when new release of this repository was published. The Workflow can create manifests of the new release and submit to microsoft/winget-pkgs.
Alternatives
Nope. I would prefer the above sulution.
Additional context