mirror of
https://github.com/hanzoai/docs.git
synced 2026-08-05 04:12:57 +00:00
zeekayandHanzo Dev
cee85e1732
.github/workflows held 19 files; it holds sync.yml alone now, the canonical push-refs workflow from universe infra/ci/sync.yml. What it replaced was a mirror-sync nudge documenting GitHub as upstream and asking the forge to pull. Thirteen workflows moved into .hanzo/workflows unchanged — byte-identical, so git records them as pure renames. runs-on is untouched: the forge's runner answers hanzo-docs-build-linux-amd64. That covers the only checks (lint, test), the only publisher of the ~30 npm packages (release), the daily pricing commit (sync-zen-pricing), and the nine sibling static sites, each of which is the ONLY deploy of its host. Those nine still reach Cloudflare Pages; they move to images one host at a time, because cf-zones declares only three of the nine and an App CR with a guessed host is wrong even while inert. LLM.md carries the list and the steps. deploy-docs.yml becomes deploy.yml and only builds and pushes. It had patched `app docs` with kubectl and waited on the rollout, and it built the image from a heredoc Dockerfile pinned to static:0.4.1 while the repo's own Dockerfile — the one the fabric builds — pinned v0.5.1. The recipe lives in the Dockerfile alone now; the workflow runs it, gates the export by reading /public out of the built image so what is checked is what serves, and pushes only if the gate passes. ghcr auth is REGISTRY_TOKEN, since a forge-issued GITHUB_TOKEN authenticates nothing there. The Dockerfile takes APP, so every static site in the monorepo builds one way and the nine siblings need no new Dockerfile when they flip. Deleted four workflows that could not have worked: deploy-liquid-docs and deploy-zap-docs build apps/liquid and apps/zap-docs, neither of which exists (liquid's Cloudflare job was already `if: false`), and fix-cf-domain and setup-gui-domain are dispatch-only one-shots calling the decommissioned Infisical /api/v3/secrets/raw route. Also corrects three changesets that named packages absent from the workspace, which made `changeset version` fail and release.yml publish nothing: @hanzo/zen-models -> @zenlm/models (sync-zen-pricing.yml wrote that name every day), and fumadocs-mdx / @fumadocs/content -> @hanzo/docs-mdx / @hanzo/docs-content per the rename rule in LLM.md. Co-authored-by: Hanzo Dev <dev@hanzo.ai>