winget: automatically publish releases #590
Merged
Conversation
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
Adds a new GitHub action that automates the publishing of new winget manifests. The workflow is triggered when a release is published and requires a repository secret to be set that has public repo access.
dgageot
approved these changes
Oct 23, 2025
Member
|
@chelnak I'm not sure I understand what needs to be configured from the link you shared |
Contributor
Author
Oh I must have copied the wrong link. I'll find the correct one! |
Contributor
Author
|
Here's the correct doc: You'll need a GitHub token that has public repo access because it will create a PR to the The workflow in this PR expects a secret named IIRC, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds a new GitHub action that automates the publishing of new winget manifests.
The workflow is triggered when a release is published and requires a repository secret to be set that has public repo access.
Info on requirements for the token can be found here.
I made the assumption that your tags will always be your release version (that seems to be the case so far).