Publish to winget

[someh2705]

Is your feature request related to a problem? Please describe.
Please support installation using winget-cli.

Describe the solution you'd like
winget-releaser makes it easy to automate deployments.

[lazysegtree]

@yorukot Do we want to do this before new release ?

[yorukot]

@yorukot Do we want to do this before new release ?

I don't think this is necessary.

[lazysegtree]

I dont know what exactly is needed to publish to winget, and how much are the efforts.

[someh2705]

First of all, please accept my apologies—English is not my first language.

To publish Superfile through winget-releaser, the package needs to be present in microsoft/winget-pkgs at least once.
The easiest way to create—and even submit—the required manifests is to use the wingetcreate tool:

wingetcreate new https://github.com/yorukot/superfile/releases/download/v1.2.1/superfile-windows-v1.2.1-amd64.zip https://github.com/yorukot/superfile/releases/download/v1.2.1/superfile-windows-v1.2.1-arm64.zip

Note: I have already tried running wingetcreate, but it failed to parse the archives. Although other ZIP-based packages such as chezmoi work fine, Superfile’s internal ZIP structure appears to be different. I am not sure whether converting the installer to MSI or adjusting the ZIP layout would be the cleaner solution

Once the initial PR is merged into winget-pkgs, the rest can be fully automated with winget-releaser.
The steps are:

1. Generate a Classic Personal Access Token (PAT) with public_repo scope.

2. Fork winget-pkgs into the same GitHub account / organisation.

3. Add the PAT as a secret in your Superfile repository (e.g., SPF_PAT).

4. Add a GitHub Actions workflow like the one below.

jobs:
  winget:
    name: Publish WinGet package
    runs-on: ubuntu-latest
    steps:
      - name: Submit package to Windows Package Manager Community Repository
        uses: vedantmgoyal2009/winget-releaser@v2
        with:
          identifier: Yorukot.Superfile
          installers-regex: '\.(zip|msi)$'      # Adjust if you switch to MSI
          version: ${{ inputs.tag_name || github.event.release.tag_name }}
          release-tag: ${{ inputs.tag_name || github.event.release.tag_name }}
          token: ${{ secrets.SPF_PAT }}

After this setup, publishing a new release tag will automatically open a PR in winget-pkgs for each version.

Thank you very much for your time and for considering this request.

[claykom]

Created initial pull request to add new package for amd64 package the manifest. I'm later going to update with the rest of the package and look into this further.
microsoft/winget-pkgs#265169

[lazysegtree]

Thanks @claykom Please reach out to me if you have any question regarding superfile, or any of our packaging code needs to be updated