Publish Windows binary + add to scoop bucket for parity with brew install #52

New issue

Closed

opened 2026-05-23 20:55:27 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-23 20:55:27 +00:00

Owner

Originally filed by @coilysiren on 2026-05-10T06:59:46Z - https://github.com/coilysiren/repo-recall/issues/72

Problem

repo-recall's release pipeline today is Mac/Linux only:

Releases are consumed via `brew install coilysiren/tap/repo-recall` from `coilysiren/homebrew-tap`.
`brew services` manages the daemon on Mac.

There is no Windows install path. On the Windows host repo-recall must currently be built from source via `cargo install --git https://github.com/coilysiren/repo-recall` (works, but doesn't pin to release tags and doesn't share the brew flow's CI provenance).

Proposed fix

Mirror the brew-tap architecture with a Scoop bucket. Pairs with the parallel coily issue at coilysiren/coily#107 - same bucket repo (`coilysiren/scoop-bucket`) hosts both manifests.

Two pieces specific to repo-recall:

Add a Windows build job to release CI. Cross-compile `repo-recall.exe` (windows-amd64, optionally arm64) and upload as a release asset alongside the existing tarball. `build.rs` should already pick up `REPO_RECALL_VERSION` env var so the version embedding works the same way.
Add `bucket/repo-recall.json` to `coilysiren/scoop-bucket` (once it exists per coily#107) pointing at the release-asset URL with `autoupdate` block. Scoop polls GitHub releases and bumps the manifest itself.

Windows host one-time setup after the bucket exists:

`scoop bucket add coilysiren https://github.com/coilysiren/scoop-bucket`
`scoop install repo-recall`

Updates via `scoop update repo-recall`. Daemon management on Windows is out of scope (no `brew services` equivalent - document "run in a long-lived terminal or use Task Scheduler" in the README).

Sequencing

Blocked on coily#107 for the bucket repo to exist. Build-job piece can land independently.

Out of scope

`brew services` parity. Documented as a gap in #71.
Signed binaries (Authenticode). Defer until SmartScreen friction shows up.
README/Makefile `brew` and `open` fixes - those are scoped to #71.

coilysiren/coily#107 - parent issue for the scoop bucket itself
coilysiren/repo-recall#71 - sibling cosmetic fixes

_Originally filed by @coilysiren on 2026-05-10T06:59:46Z - [https://github.com/coilysiren/repo-recall/issues/72](https://github.com/coilysiren/repo-recall/issues/72)_ ## Problem repo-recall's release pipeline today is Mac/Linux only: - Releases are consumed via \`brew install coilysiren/tap/repo-recall\` from \`coilysiren/homebrew-tap\`. - \`brew services\` manages the daemon on Mac. There is no Windows install path. On the Windows host repo-recall must currently be built from source via \`cargo install --git https://github.com/coilysiren/repo-recall\` (works, but doesn't pin to release tags and doesn't share the brew flow's CI provenance). ## Proposed fix Mirror the brew-tap architecture with a Scoop bucket. Pairs with the parallel coily issue at [coilysiren/coily#107](https://github.com/coilysiren/coily/issues/107) - same bucket repo (\`coilysiren/scoop-bucket\`) hosts both manifests. Two pieces specific to repo-recall: 1. **Add a Windows build job to release CI.** Cross-compile \`repo-recall.exe\` (windows-amd64, optionally arm64) and upload as a release asset alongside the existing tarball. \`build.rs\` should already pick up \`REPO_RECALL_VERSION\` env var so the version embedding works the same way. 2. **Add \`bucket/repo-recall.json\` to \`coilysiren/scoop-bucket\`** (once it exists per coily#107) pointing at the release-asset URL with \`autoupdate\` block. Scoop polls GitHub releases and bumps the manifest itself. Windows host one-time setup after the bucket exists: - \`scoop bucket add coilysiren https://github.com/coilysiren/scoop-bucket\` - \`scoop install repo-recall\` Updates via \`scoop update repo-recall\`. Daemon management on Windows is out of scope (no \`brew services\` equivalent - document "run in a long-lived terminal or use Task Scheduler" in the README). ## Sequencing Blocked on coily#107 for the bucket repo to exist. Build-job piece can land independently. ## Out of scope - \`brew services\` parity. Documented as a gap in [#71](https://github.com/coilysiren/repo-recall/issues/71). - Signed binaries (Authenticode). Defer until SmartScreen friction shows up. - README/Makefile \`brew\` and \`open\` fixes - those are scoped to [#71](https://github.com/coilysiren/repo-recall/issues/71). ## Related - [coilysiren/coily#107](https://github.com/coilysiren/coily/issues/107) - parent issue for the scoop bucket itself - [coilysiren/repo-recall#71](https://github.com/coilysiren/repo-recall/issues/71) - sibling cosmetic fixes

coilysiren referenced this issue

2026-05-23 20:55:28 +00:00

Repo-set filter args on recall_action_required and recall_refresh #59

coilysiren added the

label

2026-05-31 01:55:01 +00:00

coilysiren added

and removed

labels

2026-06-04 08:16:38 +00:00

coilysiren commented

2026-06-17 08:24:29 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:24:29 +00:00