ci: add automated WinGet publishing to CD#2017
Open
rafaucau wants to merge 1 commit into
Open
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
This PR requires repository setup before it can work.
See Notes for Reviewers.
📌 What Does This PR Do?
Adds a WinGet publishing job to the CD workflow.
On tagged releases, the workflow will submit a WinGet manifest PR to microsoft/winget-pkgs using vedantmgoyal9/winget-releaser.
🔍 Context & Motivation
Keeps the WinGet package updated automatically after releases, without relying on the community to submit updates manually.
🛠️ Summary of Changes
wingetCD job for tagged releases.📂 Affected Areas
🔗 Related Issues or PRs
#1844 (comment)
📝 Notes for Reviewers
Before this can work, the repository needs:
WINGET_TOKEN: classic GitHub PAT withpublic_repo.WINGET_USER: GitHub username owning a fork ofmicrosoft/winget-pkgs.Recommended setup: use a dedicated bot account (eg.
azjezz-bot/carthage-software-bot), fork winget-pkgs there, and generate the PAT from that account instead of a maintainer’s primary account for better security.