deepchat-release

# DeepChat Release ## Overview Follow the repository-specific DeepChat release process. Prepare release metadata on `dev`, keep `CHANGELOG.md` concise, and publish through the documented fast-forward flow instead of merge commits on `main`. ## Start With Repo State Inspect git state before changing anything: - Check the current branch and working tree. - Check whether `release/<version>` exists locally or on `origin`. - Check whether `v<version>` exists locally or on `origin`. If a local or remote tag already exists on the wrong commit, stop and ask before replacing it. ## Choose The Release Mode Pick the mode that matches the user's request and current git state: 1. `prepare metadata` Update `package.json`, `CHANGELOG.md`, and the release notes commit on `dev`. 2. `cut release branch` Create `release/<version>` from the release-ready commit on `dev` and push it. 3. `update existing release branch` Use this when the release branch already exists but metadata changed afterward. Commit on `dev`, move `release/<version>` to the new `dev` commit, and force-push only the disposable release branch. 4. `publish` Use this only after the release PR is approved. Fast-forward `main`, create the version tag on the same commit, push the tag, and then delete the temporary release branch. Use [references/release-checklist.md](references/release-checklist.md) for exact commands. ## Update Release Metadata When preparing a release on `dev`: - Update `package.json` to ...