Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open Beginner friendly
#1,714 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
github-actions
Domain
ci-cd, release

Research direction

Start with the provided winget-releaser workflow and verify the repository’s release event and Windows installer artifact naming. Configure the workflow with the CapSoftware.Cap identifier, installer regex, and WINGET_ACC_TOKEN secret, then validate it by publishing a release and confirming that winget-releaser submits the package update.

Written by the indexing model from the issue text.

Description

PR https://github.com/microsoft/winget-pkgs/pull/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

Dominant language
Rust
Stars
22.5k
Forks
1.9k
Avg merge
6h 33m
Merged PRs (30d)
77

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CapSoftware/Cap

All issues in CapSoftware/Cap

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.