Files
zeekayandHanzo Dev d42512af48 cd: publish the CD surface under its real name
The package was never published under EITHER name — `npm view @hanzo/gitops`
and `@hanzo/cd` both returned E404 — so `pkg/ui/src/gitops.ts`
(`export * from '@hanzo/gitops'`) and the `>=0.1.0` peer dep pointed at
nothing and broke every clean install of @hanzo/ui.

Publishing exposed a second break one level down: @hanzo/gitops peers on
@hanzo/canvas >=0.2.0, and the registry still had canvas at 0.1.0 while the
monorepo was on 0.2.1. Publishing the first package alone only moved the
ETARGET deeper. Both are now on the registry, and a clean
`npm install @hanzo/[email protected]` resolves — 673 packages, no errors.

pkgs/gitops -> pkgs/cd and @hanzo/gitops -> @hanzo/cd: the surface is the CD
surface (cd.hanzo.ai, apps/cd), and the old name only ever described the
mechanism. Every reference in the monorepo moved with it; the old name is
deprecated on npm pointing here rather than left as a second way to install
the same code.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-27 20:26:53 -07:00
..

@hanzo/cd

A presentational, data-prop-driven React surface for a full CD/GitOps console — a clean-room port of the Argo CD UI (Apache-2.0; see NOTICE). Every component takes typed props and renders; it never fetches. The embedding app wires the Hanzo native CD API (/v1/gitops) and maps its rows into these view-models.

import {
  GitopsAppList,      // applications grid/table (health, sync, revision, search)
  GitopsAppDetails,   // the app view shell (header + tree + node panel + sync)
  GitopsAppTree,      // resource-tree topology (health/sync color-coded, pan/zoom)
  GitopsNodeInfo,     // node drill-in: manifest / diff / events / logs
  GitopsSyncPanel,    // sync + rollback panel
  GitopsRollbackDialog,
  GitopsDiffView,     // colorized desired-vs-live unified diff
  ResourceNode,       // a single resource card (kind + health + sync)
  HealthBadge,        // Healthy / Progressing / Degraded / Suspended / Missing / Unknown
  SyncBadge,          // Synced / OutOfSync / Unknown
  GitopsStyles,       // one <style> tag: theme-aware CSS for the whole surface
} from '@hanzo/cd'

Design

Two orthogonal status axes, exactly as Argo CD models them — never conflated:

  • Health — Healthy | Progressing | Degraded | Suspended | Missing | Unknown
  • Sync — Synced | OutOfSync | Unknown

The pure folds (foldHealth, foldSync, buildResourceGraph, classifyDiff) are React-free and unit-tested in isolation, importable without pulling in any component:

import { foldHealth, foldSync, buildResourceGraph, classifyDiff } from '@hanzo/cd/pure'

The resource-tree topology reuses @hanzo/canvas's deterministic layered layout (layoutGraph) — no separate graph dependency. Nodes are laid out left-to-right by parent references (Application → Service → Deployment → ReplicaSet → Pod, plus Ingress, ConfigMap, certificates…) and color-coded by health and sync.

Theming

Presentational and theme-aware. Mount <GitopsStyles /> once (or inline GITOPS_CSS); drive the theme prop off your app's resolved theme. Status colors are semantic (Argo CD hues) and overridable via the healthPalette / syncPalette props. Migrates cleanly to @hanzo/gui primitives when that base lands — the components are clean-room React over a small scoped stylesheet.