silo-release-publish

# Publishing a Silo release Silo app releases land as **drafts** on purpose — a soak-test checkpoint before they go public (see `apps/docs/guide/release-channels.md`). Publishing is a separate, manual step, and it is the moment the release becomes real: GitHub's "Latest" slot, the website download button, the docs download links, and every existing install's auto-updater all follow `/releases/latest` immediately. Because drafts accumulate silently, the version you're asked to publish is often **not** one version ahead of what users are running. Always establish the gap before writing notes. > Package releases (`sdk-*`, `git-api-*`) are **pre-releases** and are published > by CI. This skill is only for `silo-v*` app releases. ## 1. Establish the gap ```sh gh release list --limit 10 gh api repos/silo-code/silo/releases --jq '.[] | select(.draft==false) | select(.tag_name|startswith("silo-")) | .tag_name' | head -3 ``` The first published `silo-v*` tag is what users are actually on. Every draft between it and the one you're publishing is a version whose changes ship silently unless you fold them into the notes. ## 2. Verify the draft is complete ```sh gh release view silo-vX.Y.Z --json name,isDraft,isPrerelease,tagName,assets \ --jq '"draft:\(.isDraft) pre:\(.isPrerelease)", (.assets[] | "\(.name) \(.size) \(.state)")' ``` Do not publish unless **all** of these are present and `uploaded`: - `latest.json` — the updater manifest - macOS: `Silo_X.Y.Z_aarch64.dmg`, `Si...