These must exist before the first tag, or the release fails at the publish step.
-
Package-manager repos — goreleaser writes formulas into repos that must already exist:
gh repo create runtimez-com/homebrew-tap --public \ --description "Homebrew formulas for runtimez tools" gh repo create runtimez-com/scoop-bucket --public \ --description "Scoop manifests for runtimez tools"
-
Initialise both repos. A formula cannot be pushed into a repo with no commits and no default branch:
gh api -X PUT repos/runtimez-com/homebrew-tap/contents/README.md \ -f message="init" -f content="$(printf '# runtimez Homebrew tap\n' | base64)" gh api -X PUT repos/runtimez-com/scoop-bucket/contents/README.md \ -f message="init" -f content="$(printf '# runtimez Scoop bucket\n' | base64)"
-
A token that can write to them. The default
GITHUB_TOKENin Actions is scoped to this repo only, so publishing a formula into another repo needs its own credential — and the config must name it (token:under eachrepository:), or goreleaser silently falls back to the default one and fails with a 403.A classic PAT with the
reposcope is the path of least resistance. A fine-grained PAT also works but must nameruntimez-comas its resource owner, grantcontents: writeon both tap repos, and be approved by an org owner — until that approval lands it returns 401, which looks identical to a wrong token.gh secret set TAP_GITHUB_TOKEN --repo runtimez-com/runtimez-cli gh secret list --repo runtimez-com/runtimez-cli # confirm it exists
An unset secret resolves to an empty string rather than failing, so the release preflight checks it can actually reach both repos before anything is built.
-
Make this repo public, so
brew install, Scoop andinstall.shwork without a token:gh repo edit runtimez-com/runtimez-cli --visibility public --accept-visibility-change-consequences
Check the history first — going public exposes every commit, not just the current tree.
git tag -a v0.1.0 -m "rtz v0.1.0"
git push origin v0.1.0The tag triggers .github/workflows/release.yml, which builds six binaries
(darwin/linux/windows × amd64/arm64), signs the checksums with cosign, and publishes the
GitHub Release, the Homebrew formula, the Scoop manifest, and deb/rpm/apk packages.
Dry-run the whole thing without publishing:
goreleaser release --snapshot --cleanA release can upload every artifact and still fail at the tap push. The artifacts are already public at that point, so re-cut only if the tag is minutes old and unconsumed — otherwise fix the cause and ship the next patch version.
Because goreleaser reads .goreleaser.yaml from the checked-out ref, a config fix only takes
effect in a tag that contains it. Re-running workflow_dispatch against an old tag replays
the old config.
brew install runtimez-com/tap/rtz # macOS, Linux
scoop bucket add runtimez https://github.com/runtimez-com/scoop-bucket && scoop install rtz
curl -fsSL https://raw.githubusercontent.com/runtimez-com/runtimez-cli/main/install.sh | shThen:
rtz login # hosted backend (app.runtimez.io) by default
rtz login --api https://runtimez.internal.example.com # self-hostedChecksums are signed keylessly with cosign, so a customer can confirm a download came from this repo's release workflow and not from a mirror:
cosign verify-blob \
--certificate checksums.txt.pem \
--signature checksums.txt.sig \
--certificate-identity-regexp 'https://github.com/runtimez-com/runtimez-cli/.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
checksums.txtThe version is stamped from the git tag at build time. rtz version on an untagged build
reports dev, which is how you tell a local build from a released one.