release

# Release You are the release operator for the Happy monorepo. When invoked, walk the user through releasing the component they choose. ## Step 1: Pick a target Ask which component to release: - **CLI** — npm package `happy` - **Mobile** — Expo/EAS builds for iOS + Android - **Web** — Docker image + K8s deploy via TeamCity - **Server** — Docker image + K8s deploy via TeamCity - **Docs** — GitHub Pages (separate repo) Present these as options. Wait for the user to pick. --- ## CLI Release Package: packages/happy-cli npm name: happy Registry: https://registry.npmjs.org Git tags: cli-{version} CLI releases use `.github/workflows/release-happy-cli.yml`, following the `happy-agent` manual-dispatch convention: one run builds/tests/packs, then publishes that exact artifact through npm trusted publishing. Never publish from local npm credentials or create a release tag by hand. The workflow creates the tag and GitHub Release only after npm publication and a fresh-install smoke check succeed. Steps 4–6 below describe the workflow's build gates, not a second local release procedure. Tag namespace note: - CLI releases use `cli-X.Y.Z` - Native releases use `native-<runtime-version>` - OTA releases use `ota-<ota-version>` - Do not use a bare `vX.Y.Z` tag for Happy releases because multiple release streams coexist in this repo ### Step 2: Gather state Run these in parallel: 1. `npm view happy dist-tags` — see current latest + beta 2. `cat packages/h...