wharfy 0.2.4 — every channel actually ships now

Polish since 0.1.0 (0.2.0–0.2.4 folded in). Scoop added, apt/rpm actually distributable, winget submitted. The notable fixes as problem → before → after.

apt/rpm couldn’t ship to fury.io

• Problem: fury uses different hosts for upload (push.fury.io) and delivery (apt.fury.io / yum.fury.io), but wharfy could hold only one URL, so publish broke.
• Before: a single apt.repo was used for both upload and probing → broken on fury.
• After: apt: {provider: fury, user: <name>} derives the push and delivery URLs for you (raw two-URL config also works).

status couldn’t detect the version on fury

• Problem: the probe hard-coded dists/stable/..., which 404s on fury’s flat repo (/Packages) — so a published package was reported as “not published”.
• Before: official layout only, returning the first (oldest) match.
• After: tries flat then official layout, and picks the highest of multiple versions.

No heads-up when a newer version exists

• Problem: wharfy version only printed the current version.
• Before: no update notice.
• After: a best-effort check against the latest release surfaces an upgrade in the next: block.

Tokens had to be passed via env every time

• Problem: the fury token could only come from an env var — an export in another terminal didn’t reach the run, and the value tended to linger in shell history.
• Before: PACKAGE_REPO_TOKEN (env) only.
• After: wharfy auth fury stores it in the OS keychain via a hidden prompt; publish resolves env → keychain (CI keeps using env).

Getting it

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