Add Winget Releaser workflow

[sitiom]

This action automatically generates manifests for Winget Community Repository (microsoft/winget-pkgs) and submits them.

Before merging this:

1. Add a classic PAT with public_repo scope as a repository secret named WINGET_TOKEN.

2. Fork https://github.com/microsoft/winget-pkgs under @sharkdp. The action will use that fork for making a branch and creating a PR with the upstream winget-pkgs repository on every release.
3. Install Pull on the winget-pkgs fork to ensure that it is constantly updated.

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).

• Resolves WinGet-based installation #307

[sharkdp]

Thank you. I would first like to understand if it's really necessary that I personally maintain this (I'd rather not, if possible). Couldn't that GA action run on a fork (of hyperfine, not winget - kept up to date by the pull action mentioned above) created by someone else?

[sitiom]

I would first like to understand if it's really necessary that I personally maintain this

If you want the Winget package to be updated, that is. There isn't any built-in automation to Winget, unlike Scoop.

Couldn't that GA action run on a fork (of hyperfine, not winget - kept up to date by the pull action mentioned above)

That's not how it works. The action submits a PR to https://github.com/microsoft/winget-pkgs via your winget-pkgs fork.

[sitiom]

@sharkdp Failed. The binaries weren't available in the releases: https://github.com/sharkdp/hyperfine/actions/runs/4424630811. Rerun the workflow again once you have added them.

[sharkdp]

Well, the binaries are added by another GA pipeline. Maybe that pipeline can "wait" for the other one somehow? Or be delayed?

[sitiom]

I think I should've workflow should've been added inside https://github.com/sharkdp/hyperfine/blob/master/.github/workflows/CICD.yml instead.

[sharkdp]

It failed again

[sitiom]

It seems like you didn't add the WINGET_TOKEN secret in this repo.

[sitiom]

I have manually created a PR of the new version for now: microsoft/winget-pkgs#99531

[sharkdp]

It seems like you didn't add the WINGET_TOKEN secret in this repo.

Oh, I missed that part in step 2. For future PRs, I would suggest to split that into two steps. Fixed now.

[sitiom]

Oh, I missed that part in step 2

It's actually step 1 😅

1. Add a classic PAT with public_repo scope as a repository secret named WINGET_TOKEN.