Windows is where most Cutawan installs happen. A winget package lets people run:
winget install JeremySNR.Cutawan
The app is not code-signed yet, which winget allows. Users will still see a SmartScreen prompt on first launch.
The first listing is a pull request to microsoft/winget-pkgs. Generate the three YAML files from the latest GitHub release:
node scripts/print-winget-manifest.mjs --out .tmp/wingetThen either:
- install wingetcreate and submit
(
wingetcreate submit .tmp/winget), or - open a PR against
microsoft/winget-pkgsundermanifests/j/JeremySNR/Cutawan/<version>/with those three files.
Package identifier: JeremySNR.Cutawan.
Once the package exists, set two repository secrets/variables:
| Name | Where | Value |
|---|---|---|
WINGET_TOKEN |
Actions secret | A PAT with public_repo that can open PRs on a fork of winget-pkgs |
WINGET_PACKAGE_ID |
Actions variable | JeremySNR.Cutawan |
The Release workflow then runs
winget-releaser after each GitHub Release so the manifest stays current.
Leave WINGET_PACKAGE_ID empty until the first package is accepted, otherwise
the job would try to update a package that does not exist yet.