release

# Release Process for grepai This skill guides you through creating a new release. **All output must be in English.** ## When to Use This Skill Invoke this skill when: - User asks to "create a release" - User asks to "publish a new version" - User asks to "bump the version" - User mentions "release" in the context of versioning ## Release Workflow ### Step 1: Verify CI on Main Check that all CI checks pass on main: ```bash gh run list --branch main --limit 1 --json status,conclusion,name ``` **STOP if CI is not green.** Ask the user to fix issues first. ### Step 2: Get Current Version and Changes Get the latest release: ```bash gh release list --limit 1 ``` List merged PRs since last release: ```bash gh pr list --state merged --base main --json number,title,author,mergedAt,labels --limit 50 ``` Display a summary of changes categorized by type (feat, fix, docs, etc.). ### Step 3: Determine Version Type | Change Type | Version Bump | |-------------|--------------| | Breaking changes | **Major** (vX+1.0.0) | | New features (`feat`) | **Minor** (vX.Y+1.0) | | Bug fixes (`fix`) | **Patch** (vX.Y.Z+1) | | Docs/chore only | Usually no release needed | **Ask user confirmation** before proceeding. ### Step 4: Update Version Files #### 4.1 CHANGELOG.md Add new section after `## [Unreleased]`: ```markdown ## [X.Y.Z] - YYYY-MM-DD ### Added - **Feature Name**: Description (#PR) - @author ### Fixed - **Fix Name**: Description (#PR) - @author ``` Update comparison li...