Add Winget Releaser workflow

[sitiom]

• Continuation of Add Winget in installation docs #267

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

[rhysd]

@sitiom Can you remove 4ec176a? It is not related to this PR. I think we should focus on winget release workflow only in this PR.

[sitiom]

@rhysd Updates on this? I have manually created a PR on the new version for now: microsoft/winget-pkgs#101511

[rhysd]

Ah, I'm sorry for this issue remaining open. Due to my personal reason, it is difficult to respond any issues/PRs for now. But I'll take a look at this within this week.

[rhysd]

I setup a token and fork repository. I'll try the first releaese.

[sitiom]

Did you install the Pull app on your fork? https://pull.git.ci/process/rhysd/winget-pkgs is showing "Not found."

[rhysd]

@sitiom I ran the action and the PR was created. If you have time, would you check the manifest submitted in the PR is correct? I'm not familiar with the manifest scheme.

microsoft/winget-pkgs#102052

[sitiom]

@sitiom I ran the action and the PR was created. If you have time, would you check the manifest submitted in the PR is correct? I'm not familiar with the manifest scheme.

microsoft/winget-pkgs#102052

Looks good. The CI should fail if there is some error installing the manifest.

[rhysd]

OK, thanks for checking that. It seems to work fine.

[sitiom]

@rhysd Wait, I just noticed that the version of the manifest you created includes the v prefix, which is incorrect. I have created a PR to fix the separate Winget workflow: #293.