Add winget manifest generator and release automation - #57
Merged
Conversation
Windows is most of the downloads. Generate a winget-pkgs YAML trio from the GitHub release, document the first submit, and optionally update the package on later releases once WINGET_PACKAGE_ID and WINGET_TOKEN are set. Addresses #47 Co-authored-by: Jeremy Smith <JeremySNR@users.noreply.github.com>
JeremySNR
marked this pull request as ready for review
September 6, 2026 11:33
# Conflicts: # CHANGELOG.md
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: Winget job uses branch as tag
- Added checkout and a package.json version step so winget-releaser receives release-tag v$version instead of falling back to github.ref_name (main) on non-tag runs.
You can send follow-ups to the cloud agent here.
Reviewed by Cursor Bugbot for commit 3344f06. Configure here.
| with: | ||
| identifier: ${{ vars.WINGET_PACKAGE_ID }} | ||
| installers-regex: '\.exe$' | ||
| token: ${{ secrets.WINGET_TOKEN }} |
Contributor
There was a problem hiding this comment.
Winget job uses branch as tag
Medium Severity
The winget job never passes release-tag, so winget-releaser falls back to github.ref_name. Tag pushes resolve correctly, but a Release v commit or workflow_dispatch from main looks up a release named main and publishing fails. The notes job already reads the version from package.json for this same workflow.
Reviewed by Cursor Bugbot for commit 3344f06. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
Addresses #47. Adds:
scripts/print-winget-manifest.mjs— generates the three winget-pkgs YAML files from a GitHub release (tested against v0.7.0’sClipForge-Setup-0.7.0.exe)winget-releaserafter the first listing existsThis cannot complete the first
microsoft/winget-pkgsPR from here (that needs a PAT that can fork that repo). Once that listing is accepted, setWINGET_PACKAGE_ID=JeremySNR.ClipForgeandWINGET_TOKEN, and later releases stay in sync.Why?
Most downloads are the Windows installer.
winget install JeremySNR.ClipForgeis how those users expect to install.How did you test it?
npm test(includingtests/wingetManifest.test.ts)npm run typechecknpm run lintnode scripts/print-winget-manifest.mjs 0.7.0 --out …against the live v0.7.0 releaseAnything to watch out for?
The winget job is a no-op until
WINGET_PACKAGE_IDis set, so ordinary releases do not fail. The app is still unsigned; winget allows that, SmartScreen will still prompt.