ci: add winget releaser workflow
This action automatically generates manifests for Winget Community Repository (microsoft/winget-pkgs) and submits them.
The Zen Browser package is being added to Winget (https://github.com/microsoft/winget-pkgs/pull/168940, https://github.com/microsoft/winget-pkgs/pull/168942), and this workflow will be used to update it.
Before merging this:
- Ensure the
${{ secrets.DEPLOY_KEY }}token has thepublic_repopermission:

- Fork https://github.com/microsoft/winget-pkgs under @zen-browser. The action will use that fork for making a branch and creating a PR with the upstream winget-pkgs repository on every release.
- Install Pull on the winget-pkgs fork to ensure that it is constantly updated.
If you want to see an example of a PR created using this action, see microsoft/winget-pkgs/pulls (Pull request has been created with WinGet Releaser).
- Ensure the ${{ secrets.DEPLOY_KEY }} token has the public_repo permission
Could we get that done in the CI by using the PAT from GH actions and specifying it's permissions?
Sidenote, ZenBrowser.Zen also exists, I don't know if we can do something about there now being 2 IDs for the browser.
Could we get that done in the CI by using the PAT from GH actions and specifying it's permissions?
No, you can't. The PAT is used to make a commit and create a PR from an external repo.
Sidenote, ZenBrowser.Zen also exists, I don't know if we can do something about there now being 2 IDs for the browser.
- https://github.com/microsoft/winget-pkgs/pull/169157
Would using on: release avoid/fix the issue? So rather than it running with the main pipeline, it would run by itself whenever a new release is out. (Example https://github.com/microsoft/devhome/blob/94fde2349d7666575f28daf54451668f0acdbf4c/.github/workflows/winget-submission.yml#L3C1-L6C23).
How would we sign it though? My license key is physical
The action would only run when you publish a release, so you'd still be able to sign your stuff
I just want to get everything signed and working before expanding to more windows sites... But this will be merged
Closed?
Try changing the base branch to dev or opening a new PR