4 Commits
Author SHA1 Message Date
zeekayandHanzo Dev 21b511f665 CI/CD takes the pipeline's default runner
ci / python (push) Canceled after 0s
ci / go (push) Canceled after 0s
ci / wheel (3.12) (push) Canceled after 0s
ci / wheel (3.9) (push) Canceled after 0s
Hanzo CI/CD / cicd (push) Canceled after 0s
CI/CD / cicd (push) Canceled after 0s
deploy / image (push) Canceled after 0s
linux-amd64 is the label the forge starts runners for. hanzo.yml's
comments now name the workflow paths that exist.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-11 14:05:24 -07:00
zeekayandHanzo Dev 3894aaaea6 A hanzo_agents tag publishes the SDKs
The wheel joins hanzo.yml's pypi lane and CI starts on hanzo_agents-v*
tags. release.yml publishes @hanzo/agents from the same tag, with the npm
credential read from KMS. The Go module resolves from an sdk/go/v* tag
beside it.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-11 12:12:32 -07:00
zeekayandHanzo Dev 5c7fe83dfc Release 0.1.1
0.1.0 is on PyPI unimportable -- no numpy in its metadata on 3.9, no
httpx on 3.12 -- and the fix for it has been on main since #12, reaching
nobody: pip takes the highest version, and this repo had no way to
publish a higher one. It built a wheel, installed it at both ends of its
classifiers, imported it and threw it away.

`pypi: [.]` is the lane. 0.1.1 because 0.1.0 is the highest published.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-10 21:45:38 -07:00
zeekayandHanzo Dev 95bf3c587a ci: canonical pair — hanzo.yml + forge caller
github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-06 02:36:33 -07:00