feat: add CI action for publishing package to WinGet#564
Conversation
|
Just being notified of updates to this PR :D Since 2025, a couple of things changes so I've moved the workflow to the latest recommendations. These are
I've also removed the I've also updated the PR description to better reflect what needs to be done by the maintainers. cc @dlevy-msft-sql |
dlevy-msft-sql
left a comment
There was a problem hiding this comment.
Re-approving on 8f08da5. The updates since my prior approval are all improvements: least-privilege permissions, token via env var (WINGET_CREATE_GITHUB_TOKEN) instead of inline --token, removal of the manual fork-sync step (no more <repo-owner> placeholder), and alignment with the current wingetcreate URL/arch handling. Maintainer note: the repo secret name needs to be WINGET_CREATE_GITHUB_TOKEN (renamed from WINGET_GITHUB_TOKEN in the original draft).
This PR proposes to add a GitHub action for submitting the latest stable release to WinGet as it gets published. microsoft/winget-create is used as the tool for submitting the latest package.
Steps needed from maintainers
If the maintainers approve of these changes, they will need to do the following before merging this PR:
WINGET_CREATE_GITHUB_TOKENthat's a public access token (classic) withpublic_reposcope from the user account where the winget-pkgs fork will exist for submitting a PR. Recommend using a bot account for this purpose.For reference, maintainers may see similar implemented actions in the following repos: