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/ui@8.0.12` 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 <dev@hanzo.ai>
hanzo-dev
d238cb67f9