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} 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/happy-cli/package.json | grep version` — local version 3. `git status --short` — check for dirty state 4. `git branch --show-current` — confirm branch 5. `git log --oneline -10` — recent commits for release notes context Present a summary: ``` Local version: X.Y.Z npm latest: X.Y.Z npm beta: X.Y.Z-N Branch: main Working tree: clean / dirty ``` ### Step 3: Pick channel and version Ask the user: - **Channel**: `latest` or `beta` - **Bump type**: For latest: `patch`, `...