jeff/clipwatch

Watch

Fork 0

Submit new versions to the JCOllie winget source #1

New issue

Closed

opened 2026-10-14 01:02:15 -05:00 by jeff · 2 comments

jeff commented

2026-10-14 01:02:15 -05:00

Owner

Part of jeff/winget-pkgs#4
Blocked by: jeff/winget-submit#1, jeff/winget-pkgs#8

Make clipwatch submit its own new versions to the JCOllie winget source.

1. The next release's manifest, by hand

The published JCOllie.Clipwatch 0.2.0 manifest still points at codeberg.org: its InstallerUrl, and in the default locale file PublisherUrl, PackageUrl, LicenseUrl and ReleaseNotesUrl. wingetsource check now accepts installers only from git.jcollie.dev, and the action copies the default locale file unchanged, so the codeberg URLs would carry on into every automated version.

Published versions are never edited, so the fix is the manifest for the next release (after v0.2.0), written by hand — or with wingetsource new-version and then edited — in a pull request against jeff/winget-pkgs, with every URL on https://git.jcollie.dev/jeff/clipwatch.

2. The action call in `release.yml`

After the release job has uploaded the assets, a step (or job) uses jeff/winget-submit pinned by commit, with:

identifier: JCOllie.Clipwatch
version: the tag without its leading v
installers: x64 and the clipwatch-x86_64-windows.exe asset URL of this release
release-notes-url: this release's page
token: ${{ secrets.WINGET_BOT_TOKEN }}

It is skipped for a prerelease tag; the action does not check that itself.

Done when

The release after the hand-written one opens its own submission against jeff/winget-pkgs, and that pull request passes its test check.

Part of jeff/winget-pkgs#4 Blocked by: jeff/winget-submit#1, jeff/winget-pkgs#8 Make clipwatch submit its own new versions to the `JCOllie` winget source. ## 1. The next release's manifest, by hand The published `JCOllie.Clipwatch` 0.2.0 manifest still points at codeberg.org: its `InstallerUrl`, and in the default locale file `PublisherUrl`, `PackageUrl`, `LicenseUrl` and `ReleaseNotesUrl`. `wingetsource check` now accepts installers only from git.jcollie.dev, and the action copies the default locale file unchanged, so the codeberg URLs would carry on into every automated version. Published versions are never edited, so the fix is the manifest for the next release (after `v0.2.0`), written by hand — or with `wingetsource new-version` and then edited — in a pull request against `jeff/winget-pkgs`, with every URL on `https://git.jcollie.dev/jeff/clipwatch`. ## 2. The action call in `release.yml` After the `release` job has uploaded the assets, a step (or job) uses `jeff/winget-submit` pinned by commit, with: - `identifier: JCOllie.Clipwatch` - `version`: the tag without its leading `v` - `installers`: `x64` and the `clipwatch-x86_64-windows.exe` asset URL of this release - `release-notes-url`: this release's page - `token: ${{ secrets.WINGET_BOT_TOKEN }}` It is skipped for a prerelease tag; the action does not check that itself. ## Done when The release after the hand-written one opens its own submission against `jeff/winget-pkgs`, and that pull request passes its `test` check.

jeff added a new dependency

2026-10-14 01:02:20 -05:00

jeff/winget-submit#1 - Build the submit action

jeff added a new dependency

2026-10-14 01:02:20 -05:00

jeff/winget-pkgs#8 - Set up the winget-bot submitter with a wizard

jeff referenced this issue from jeff/winget-pkgs

2026-10-14 01:02:29 -05:00

winget-submit action and winget-bot user #4

jeff added the

ready-for-agent

label

2026-10-14 01:03:57 -05:00

jeff referenced this issue

2026-10-14 01:54:43 -05:00

Submit each release to the JCOllie winget source #2

jeff referenced this issue from a commit

2026-10-14 01:54:44 -05:00

submit each release to the JCOllie winget source

jeff commented

2026-10-14 01:54:44 -05:00

Author

Owner

Change of plan for step 1: rather than writing the next release's manifest by hand, the release job runs the action from the start (PR above), and its first automated pull request against jeff/winget-pkgs gets one extra commit moving PublisherUrl, PackageUrl and LicenseUrl in the default locale file from codeberg.org to git.jcollie.dev before it is merged. The installer URL is already right, since releases are published on git.jcollie.dev. Done when that pull request passes its check and is merged.

Change of plan for step 1: rather than writing the next release's manifest by hand, the release job runs the action from the start (PR above), and its first automated pull request against jeff/winget-pkgs gets one extra commit moving `PublisherUrl`, `PackageUrl` and `LicenseUrl` in the default locale file from codeberg.org to git.jcollie.dev before it is merged. The installer URL is already right, since releases are published on git.jcollie.dev. Done when that pull request passes its check and is merged.

jeff referenced this issue from a commit

2026-10-14 02:20:40 -05:00

move clipwatch's locale URLs from codeberg.org to git.jcollie.dev

jeff commented

2026-10-14 02:33:13 -05:00

Author

Owner

Done. The v0.2.1 release's winget job opened jeff/winget-pkgs#13 as winget-bot; it got one extra commit moving the locale URLs to git.jcollie.dev, passed its check and was merged. The published source now indexes JCOllie.Clipwatch 0.2.1, served with the git.jcollie.dev installer, its matching SHA-256, and the corrected URLs. Later releases copy from 0.2.1 and need no fix.

Done. The v0.2.1 release's `winget` job opened jeff/winget-pkgs#13 as winget-bot; it got one extra commit moving the locale URLs to git.jcollie.dev, passed its check and was merged. The published source now indexes JCOllie.Clipwatch 0.2.1, served with the git.jcollie.dev installer, its matching SHA-256, and the corrected URLs. Later releases copy from 0.2.1 and need no fix.

jeff closed this issue

2026-10-14 02:33:14 -05:00