Add winget-releaser github action for auto new releases to `CapSoftware.Cap`

[jo-chemla]

PR microsoft/winget-pkgs#355128 I submitted to winget-pkgs got merged so there is now a CapSoftware.Cap package that can then simply installed by your windows userbase via

winget install CapSoftware.Cap

It would be great to setup a github action workflow into this repo so new Cap releases are automatically pushed to winget. Note this usually involves having the installer published as a github release artifact - right now I'm using a custom regex that won't work with this action, windows\-x64\-setup\.exe

The standard way to do it is to use winget-releaser (which uses Komac under the hood). It requires a Classic Github Personal Access Token with public_repo scope is created, following this link, then the Token can be added to the repo as a secret named WINGET_ACC_TOKEN. See below, that user also will have to fork the winget-pkgs repository.

Notes:
You will need to create a classic Personal Access Token (PAT) with public_repo scope. New fine-grained PATs aren't supported by the action.
Fork microsoft/winget-pkgs under the same account/organization as the project's repository. If you are forking winget-pkgs on a different account (e.g. bot/personal account), you can use the fork-user input to specify the username of the account where the fork is present.

Here is the standard action workflow file to do so

name: Publish release to WinGet
on:
  release:
    types: [released]
jobs:
  publish:
    runs-on: windows-latest
    steps:
      - uses: vedantmgoyal9/winget-releaser@latest
        with:
          identifier: CapSoftware.Cap
          installers-regex: 'windows\-x64\-setup\.exe'
          token: ${{ secrets.WINGET_ACC_TOKEN }}

Describe alternatives you've considered
Let the community maintain the package, risk being outdated recordly package on winget repo

[linear]

CAP-676

[tembo]

Thanks for setting up the winget package and providing this detailed guide!

One thing to note: Cap currently doesn't upload Windows installers to GitHub releases - they're hosted on CrabNebula Cloud instead (see the publish workflow in .github/workflows/publish.yml). The GitHub releases are draft-only for the release notes, while actual distribution happens through CrabNebula.

For the winget-releaser action to work, you'd need to either:

1. Modify the publish workflow to also upload the signed Windows NSIS installer (Cap_{version}_x64-setup.exe) as a GitHub release asset alongside the CrabNebula upload (around line 274 in publish.yml, after the SignPath signing step)

2. Use Komac directly with a custom download URL pointing to CrabNebula's CDN, though this would require figuring out the versioned URL pattern or using their API

The installer filename from Tauri is Cap_{version}_x64-setup.exe (based on productName: "Cap" in apps/desktop/src-tauri/tauri.prod.conf.json), so the regex in your workflow would need adjustment.

If option 1 is chosen, you could add something like this after the upload assets step in the Windows build matrix:

- name: Upload Windows installer to GitHub release
  if: ${{ runner.os == 'Windows' }}
  uses: softprops/action-gh-release@v2
  with:
    tag_name: cap-v${{ needs.draft.outputs.version }}
    files: target/x86_64-pc-windows-msvc/release/bundle/nsis/*.exe

Then the winget-releaser workflow would use:

installers-regex: 'Cap_.*_x64-setup\.exe$'

[jo-chemla]

I would indeed use option 1 if that's what Cap Software team thinks is best - at least that's how almost all (~50) winget packages I submitted rely on.