Publish a winget manifest for Windows installs

[JeremySNR]

Windows is where most people actually install ClipForge (the .exe accounts for the large majority of release downloads), but installing still means finding the releases page and downloading an installer.

A winget manifest would make it:

winget install ClipForge

What's involved

• Write a manifest (version, installer, locale YAML) for the current release.
• Submit a PR to microsoft/winget-pkgs. wingetcreate generates most of it from an installer URL.
• Optionally add a job to .github/workflows/release.yml so wingetcreate update runs on each release and the manifest never goes stale.

Good first issue because it needs no changes to the app itself, just packaging metadata. The installer is already built and published by the release workflow.

Worth noting the app is not code-signed yet, which winget allows but which does mean a SmartScreen prompt for users.

[JeremySNR]

Picking this up on the ClipForge side: a release-workflow job that can submit installer updates to winget-pkgs, plus docs for the first-time manifest. The first publish to microsoft/winget-pkgs still needs a one-off personal access token (WINGET_TOKEN).

[JeremySNR]

Partly done: #57 is merged, which covers the first and third bullets here.

• scripts/print-winget-manifest.mjs generates the version / installer / locale YAML trio from a GitHub release (--out DIR to write files), with unit tests in tests/wingetManifest.test.ts.
• .github/workflows/release.yml has a winget job that keeps the manifest current on later releases.
• docs/winget.md documents both paths.

Leaving this open because the second bullet — the actual PR to microsoft/winget-pkgs — has not happened, so winget install JeremySNR.ClipForge does not work yet. That step needs a fork of winget-pkgs and can't be done from this repo.

Remaining, for whoever picks it up:

1. node scripts/print-winget-manifest.mjs --out .tmp/winget against the latest release.
2. Submit those three files to winget-pkgs under manifests/j/JeremySNR/ClipForge/<version>/ (or wingetcreate submit .tmp/winget).
3. Once the listing is accepted, set the WINGET_PACKAGE_ID Actions variable to JeremySNR.ClipForge and the WINGET_TOKEN secret — the release job is gated on WINGET_PACKAGE_ID being non-empty and stays inert until then.

Two things worth a look before that first submission:

• The release job pins vedantmgoyal9/winget-releaser@v2, a mutable tag on a third-party action that receives WINGET_TOKEN. Pinning it to a commit SHA would be the safer call given what that token can do.
• The manifest declares Scope: user, which matches electron-builder's NSIS default (oneClick: true, perMachine: false) as currently configured in package.json. If the installer ever becomes per-machine, that field has to change with it.

---

Generated by Claude Code