scoop: migrate Windows .exe + scoop-bucket pipeline to forgejo #82

New issue

Open

opened 2026-05-25 06:57:36 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-25 06:57:36 +00:00

Owner

Problem

Coily's release pipeline migrated to forgejo Actions (closes #80 — pipeline runs on forgejo, cuts forgejo Releases, bumps Formula via forgejo Contents API). The brew install path is end-to-end forgejo. But the Windows scoop install path is still github-coupled and not yet ported:

Windows .exe cross-build job lives in the deleted .github/workflows/release.yml
.exe artifacts upload to github Releases as assets
The scoop manifest at coilysiren/scoop-bucket/bucket/coily.json has url: https://github.com/coilysiren/coily/releases/download/...
bump-scoop job in the old workflow rewrote that manifest via github Contents API using SCOOP_BUCKET_TOKEN

Until this lands, Windows users tracking coily via scoop are stuck on whatever version github Releases last published (v2.37.0 as of the migration). Forgejo-cut releases ship binaries nowhere reachable by scoop.

Sub-tasks

Migrate the coilysiren/scoop-bucket repo itself to forgejo (it's currently github-only, similar to homebrew-tap). Decide: keep the github mirror, or archive github after forgejo flip.
Add a windows-build job to coily/.forgejo/workflows/release.yml: cross-compile coily-windows-{amd64,arm64}.exe + sha256 sidecars and attach to the forgejo Release. Forgejo Releases supports asset uploads via POST /api/v1/repos/{owner}/{repo}/releases/{id}/assets.
Add a bump-scoop job to coily/.forgejo/workflows/release.yml: rewrite coilysiren/scoop-bucket manifest with the new tag + forgejo Release URLs + asset SHAs. Cross-repo write needs a separate forgejo PAT in SSM (one secret to provision).
Update scoop manifest URL pattern to point at https://forgejo.coilysiren.me/coilysiren/coily/releases/download/<tag>/coily-windows-<arch>.exe. Verify scoop client handles forgejo Release asset URLs (it should — they're plain HTTPS downloads).
Verify the scoop client can fetch the bucket itself from forgejo (it may need a github mirror, or scoop's bucket-add URL needs to support forgejo).

Why deferred

Coily-the-binary needed the brew path working first (Mac is canonical on the brew side, that's the priority surface). Scoop is the second-class platform and a separate concrete migration.

**Problem** Coily's release pipeline migrated to forgejo Actions (closes #80 — pipeline runs on forgejo, cuts forgejo Releases, bumps Formula via forgejo Contents API). The brew install path is end-to-end forgejo. But the **Windows scoop install path is still github-coupled** and not yet ported: - Windows `.exe` cross-build job lives in the deleted `.github/workflows/release.yml` - `.exe` artifacts upload to **github Releases** as assets - The scoop manifest at `coilysiren/scoop-bucket/bucket/coily.json` has `url: https://github.com/coilysiren/coily/releases/download/...` - `bump-scoop` job in the old workflow rewrote that manifest via github Contents API using `SCOOP_BUCKET_TOKEN` Until this lands, Windows users tracking coily via scoop are stuck on whatever version github Releases last published (v2.37.0 as of the migration). Forgejo-cut releases ship binaries nowhere reachable by scoop. **Sub-tasks** 1. Migrate the `coilysiren/scoop-bucket` repo itself to forgejo (it's currently github-only, similar to homebrew-tap). Decide: keep the github mirror, or archive github after forgejo flip. 2. Add a `windows-build` job to `coily/.forgejo/workflows/release.yml`: cross-compile `coily-windows-{amd64,arm64}.exe` + sha256 sidecars and attach to the forgejo Release. Forgejo Releases supports asset uploads via `POST /api/v1/repos/{owner}/{repo}/releases/{id}/assets`. 3. Add a `bump-scoop` job to `coily/.forgejo/workflows/release.yml`: rewrite `coilysiren/scoop-bucket` manifest with the new tag + forgejo Release URLs + asset SHAs. Cross-repo write needs a separate forgejo PAT in SSM (one secret to provision). 4. Update scoop manifest URL pattern to point at `https://forgejo.coilysiren.me/coilysiren/coily/releases/download/<tag>/coily-windows-<arch>.exe`. Verify scoop client handles forgejo Release asset URLs (it should — they're plain HTTPS downloads). 5. Verify the scoop client can fetch the bucket itself from forgejo (it may need a github mirror, or scoop's bucket-add URL needs to support forgejo). **Why deferred** Coily-the-binary needed the brew path working first (Mac is canonical on the brew side, that's the priority surface). Scoop is the second-class platform and a separate concrete migration.

coilysiren added the

label

2026-05-31 01:52:41 +00:00

coilysiren added

and removed

labels

2026-05-31 06:59:46 +00:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

coilyco-bridge/coily#82

No description provided.

Rows
Columns