Add Winget Releaser workflow#2036
Conversation
|
@tgauth Bump |
|
Thanks for working on this @sitiom I saw that microsoft/winget-pkgs#97126 uses WinGet Releaser v2 but microsoft/winget-pkgs#97419 uses Komac v1.0.5. Just curious why microsoft/winget-pkgs#97419 was created with Komac v1.0.5, rather than WinGet Releaser v2, if this workflow uses WinGet Releaser v2? It looks like WinGet Releaser has similar functionality to WinGet create, where the ReleaseNotes field of the WinGet manifest is not updated, but the ReleaseNotesURL is. I think that's fine, but are there any other limitations that I'm missing? |
Winget Releaser uses Komac behind the hood. I've made the second PR manually using Komac. In the first PR, I was testing Winget Releaser in my fork.
No, they are both updated in Komac/Winget Releaser (https://github.com/microsoft/winget-pkgs/blob/28c8a6a17d7342f0981aa3e37c7c11b8d6965819/manifests/m/Microsoft/OpenSSH/Beta/9.2.0.0/Microsoft.OpenSSH.Beta.locale.en-US.yaml#L25-L36). WingetCreate is the one with the limitation.
The biggest difference is that Komac is cross-platform while WingetCreate is not: |
|
@tgauth Did you do the prerequisites in #2036 (comment)? I don't see https://github.com/PowerShell/winget-pkgs. If you plan to use your fork instead, you need to add |
ah, ok will add that - we're using https://github.com/pwshBot/winget-pkgs |
PR Summary
This action automatically generates manifests for Winget Community Repository (microsoft/winget-pkgs) and submits them.
Before merging this:
public_reposcope as a repository secret namedWINGET_TOKEN.You can test out the action inputs in this playground.
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).
PR Context