release

# Chorus Release Process Step-by-step guide to cut a new release of Chorus. ## Prerequisites - `gh` CLI is authenticated (`gh auth status`) - Working tree is clean (`git status`) - You are on the `develop` branch ## Steps ### 1. Fetch remote and identify the diff since last release ```bash # Fetch remote tags and branches so local refs are up to date git fetch --tags origin # Find the previous release tag git tag -l 'v*' --sort=-version:refname | head -5 # List commits since previous tag on develop git log --oneline v<PREV>..develop # Review each commit for CHANGELOG-worthy changes git show --stat <commit-hash> ``` ### 2. Draft CHANGELOG and get user approval Based on the commits identified in Step 1, draft the new CHANGELOG section and **present it to the user for review**. Use this structure: ```markdown ## [X.Y.Z] - YYYY-MM-DD ### Added - **Feature name**: Description of what was added. ### Changed - **Area**: Description of what changed. ### Fixed - **Bug name**: Description of what was fixed. ### Plugin - Plugin version changes if applicable. --- ``` **Rules:** - Only include commits **after** the previous release tag - Group by Added / Changed / Fixed / Deprecated / Removed / Plugin - Omit empty groups - Each entry should start with a **bold label** followed by a concise description - Separate from the previous release section with `---` **IMPORTANT:** After drafting, show the CHANGELOG content and the proposed version number to the user. **Do NOT pro...