zeekay b12fd8cf32 deploy: repoint the Go module path to github.com/hanzoai/deploy/v3 ...

Same mechanical rename as on master, applied to the v3.4.5 release
lineage, which is the code production actually runs. Targets were
re-enumerated against this tree rather than reused from master.

This branch exists so the first Hanzo CD image is a like-for-like
cutover: identical argo-cd code, published from our registry by our CI.
Master is a different lineage — VERSION 3.6.0, 823 commits ahead of
v3.4.5 and missing 98 of its backports — so an image built there would
change the code as well as the registry. Moving the lineage is its own
change, gated separately.

go build ./cmd/... passes before and after the rename.

2026-07-16 13:59:07 -07:00

..

main.go

deploy: repoint the Go module path to github.com/hanzoai/deploy/v3

2026-07-16 13:59:07 -07:00