-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub Release Automation #1184
Comments
Great idea! It seems like there's more traction on dealing with this in #500 |
This comment has been minimized.
This comment has been minimized.
We have a new tool coming very soon (think days, not weeks) that will help with this issue. microsoft/winget-cli#157 we will include a standalone .exe you can include in CI pipelines to create/submit manifests and new package versions. |
Here is the link to the new wingetcreate tool designed to help build manifests. The PR is in progress so soon you will be able to |
I'm not sure if this applies 100% to this issue. But other package managers has great ways of handling manifest updates, such as Scoop's Autoupdate. Could be worth looking into for inspiration. |
@SonOfDiablo we would prefer Independent Software Vendors (ISVs) and publishers to produce their own manifests. The wingetcreate utility can run as an .exe in a GitHub action to generate and submit manifests. The secondary option would be to "self-serve" GitHub releases. We've added a ".package" file for #100 and I think we could extend that functionality for this scenario. |
@vedantmgoyal2009 as we get closer to having the ability to add a .packages file to support "pull" style automation vs. "push" from a publisher, we might be able to leverage some of the the work you've done. Thanks for building it open source under MIT license. That makes it much easier for us to look at how we might integrate this work into the Windows Package Manager app repository. |
I think this issue could have been closed a while back. There are a few different automated options available. Here are a couple of examples using wingetcreate: |
Description of the new feature/enhancement
Somewhat spitball of an idea, but it'd be nice to automate going from a GitHub Release -> Winget-pkgs Pull Request. A lot of OSS distributes binaries via GitHub Releases now, so it'd be one less step for them to be able to map releases.
Proposed technical implementation details
I'm not sure TBH. The ability to configure a GitHub Project + an asset -> manifest mapping, and then a Msft service that polled those endpoints respectfully and created PRs on new releases?
The text was updated successfully, but these errors were encountered: