4 Commits
Author SHA1 Message Date
zeekay 8b3c902075 Publish the console as hanzo-kms, since kms is a reserved slug
The first run on the GitHub plane gated and built the console, then the
publish stopped at "ensure project kms returned HTTP 400: slug is a
reserved subdomain and cannot be used". The admin console publishes as
hanzo-admin for the same reason; this one is hanzo-kms, and universe's
kms-static root follows it.
2026-10-16 22:47:18 -07:00
zeekay f447ec6bd5 Build on the GitHub plane again, so the console ships
The caller moved to .hanzo/workflows on 2026-09-15, but the forge mirror
of a hanzoai/* repo runs no workflows, so since then nothing gated, built
or published: kms.hanzo.ai still serves the bundle from before the move.
The one caller is .github/workflows/cicd.yml again, on hanzoai/ci
build.yml@v2 with mode delegate, reading hanzo.yml as before.
2026-10-16 22:34:46 -07:00
zooqueenandHanzo Dev 8b991fbf37 Images build at versions past the newest published tag
CI/CD / cicd (push) Waiting to run
Hanzo CI/CD / cicd (push) In progress
kms builds as 2.6.8 and kms-fetch as 0.1.1. Without a stated version the
build would take VERSION (0.159.5), a tag ghcr.io/hanzoai/kms already
holds.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 11:47:34 -07:00
zooqueenandHanzo Dev 6ba3f6d83c Build, test and publish on the forge from hanzo.yml
.hanzo/workflows/cicd.yml runs hanzoai/ci build.yml, which gates on the
Go tests and the console tests, builds the kms and kms-fetch images, and
publishes frontend/dist to the Sites plane as kms. The GitHub workflows
that did the same work are removed.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 11:33:56 -07:00