wharfy 0.13.0 — no silent, empty GUI manifest

What was wrong

A GUI project distributing through scoop hit an install error:

> scoop install <app>
ERROR '<app>' doesn't support current architecture!

The machine was 64-bit — architecture wasn’t the problem. The published manifest had no download wired at all:

{
  "version": "…",
  "architecture": {},
  "bin": "<cli>.exe",
  "shortcuts": [["<cli>.exe", "<app>"]],
  "checkver": "github"
}

scoop’s bundle path takes a portable .zip (with the .exe inside). This bundle shipped an NSIS installer (setup.exe) and no zip, so nothing matched — and wharfy published the empty-architecture manifest anyway, without saying so. The distributor only found out from a user’s failed install. winget had the same shape: no zip → an installer manifest with an empty Installers list, submitted as a PR.

The fix

publish no longer ships a manifest it couldn’t wire. When there’s no artifact a channel can install, it skips that channel and says why:

✓ scoop skipped — nothing to wire
  ⚠ channel_skipped: scoop skipped: no windows .zip wired to scoop —
    the bundle ships no portable zip (scoop needs a portable .zip, not
    an NSIS/msi installer). Ship a windows .zip bundle, or distribute
    the GUI via cask/winget

Nothing is written to the bucket, and it isn’t recorded as published. The same guard covers winget — an empty Installers list is never turned into a PR.

Where GUI installers go

wharfy’s Windows GUI path stays on the portable .zip (scoop/winget install it directly, no installer step). NSIS/msi installers aren’t wired into these channels — ship a .zip bundle for scoop/winget, or distribute the installer through the Cask / direct download.

Getting it

brew upgrade wharfy / scoop update wharfy / go install github.com/ShiroDoromoto/wharfy/cmd/wharfy@latest. On Linux, from the apt / yum repo.