prepare-release

# Prepare Release Automate the Cherry Studio release workflow: collect changes → generate bilingual release notes → update files → create release branch → trigger CI/CD. ## Arguments Parse the version intent from the user's message. Accept any of these forms: - Bump type keyword: `patch`, `minor`, `major` - Exact version: strict `x.y.z` or `x.y.z-<prerelease>` without build metadata (e.g. `1.8.0`, `1.8.0-beta.1`, `1.8.0-rc.1`) - Natural language: "prepare a beta release", "bump to 1.8.0-rc.2", etc. Defaults to `patch` if no version is specified. Always echo the resolved target version back to the user before proceeding with any file edits. - `--dry-run`: Preview only, do not create a release branch. ## Workflow ### Step 1: Determine Version 1. For an interactive local run, fetch `origin/main` and all tags, then verify that the checkout is a clean `main` at exactly `origin/main`: ```bash git fetch origin refs/heads/main:refs/remotes/origin/main --tags test "$(git branch --show-current)" = main test -z "$(git status --porcelain)" test "$(git rev-parse HEAD)" = "$(git rev-parse origin/main)" ``` Stop before editing files if any check fails. This prevents a standalone run from creating a release branch from an arbitrary or stale checkout. In GitHub Actions, use the workflow's frozen dispatch SHA and leave checkout validation to the workflow. Do not fetch or compare the later `origin/main` head. 2. Read the current version from `package.json`. Post ...