[New Feature]: Automatically publish to WinGet#839
Merged
SpartanJ merged 1 commit intoSpartanJ:mainfrom Mar 18, 2026
Merged
Conversation
- Integrates the `vedantmgoyal9/winget-releaser` action into the release workflow. - Ensures Windows users can easily install and update the application via WinGet. - Uses the generated release version and ZIP installers for publication. Signed-off-by: ❤是纱雾酱哟~ <49941141+Dragon1573@users.noreply.github.com>
Owner
|
Awesome! Thanks! I'll try to test it and merge it before the next release. |
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.
What's new?
Integrates the
vedantmgoyal9/winget-releaseraction into the release workflow.Ensures Windows users can easily install and update the application via WinGet.
Uses the generated release version and ZIP installers for publication.
Resolve [SUGGESTION][BUCKET] Winget (see #120) #286
Warning
I haven't tested the addition job(s) locally. They should work as expected.
nektos/actcan be used to run "simulated" GitHub Runners locally, butpublish_wingetjob and previous build jobs are running on different OS.actmight not suite for the local test.Important
The job uses
secrets.WINGET_TOKENto login GitHub and create pull request inmicrosoft/winget-pkgs. This GitHub Secret should be configured properly before the newer workflow file is triggered.Configure it as instructed here.