zooqueen d8841ac346 release: the tap bump writes the forge, not github ...

Its first run pushed github.com directly and left git.hanzo.ai — the canonical
copy — one commit behind, with a push mirror aimed at a github main that no
longer descended from it. Writing the canonical copy and letting the mirror
carry it to github is the only direction that keeps one history: `brew tap`
still clones github, and still gets the bump.

FORGE_TOKEN is the credential the spec re-pin already pushes this repo's own
protected main with, applied the same way (`http.extraheader`), and absent it
the step says so instead of interpolating to empty and pushing nothing. The
sidecars stay on github Releases, which is where distribution lives either way.

2026-08-15 22:22:02 -07:00

..

workflows

release: the tap bump writes the forge, not github

2026-08-15 22:22:02 -07:00