version-bump-cx

# Version Bump Workflow Automatically bump the project version, generate CHANGELOG entries from git history since the last tag, update every file that references the version, and refresh project documentation to reflect the current state. ## Codex Execution Notes - Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` for independent reads, checks, and GitHub calls. - Any user-approval phase is a hard stop: present the report/status in the final response and wait before committing, pushing, tagging, publishing, or deploying. > **VERSION RULE: Always use PATCH bumps (3.x.y → 3.x.y+1)** > NEVER use `npm version minor` or `npm version major`. > Always use: `npm version patch --no-git-tag-version` > The threshold rule: when `y` reaches 10, bump to `3.(x+1).0` — e.g. `3.4.10` → `3.5.0`. --- ## Phase 1: Determine Version ### 1. Read current version and last tag // turbo ```bash cd /home/diegosouzapw/dev/proxys/OmniRoute CURRENT_VERSION=$(node -p "require('./package.json').version") LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "") CURRENT_BRANCH=$(git branch --show-current) echo "Current version: $CURRENT_VERSION" echo "Last tag: $LAST_TAG" echo "Current branch: $CURRENT_BRANCH" ``` ### 2. Calculate new version Apply the patch bump rule: - If the current patch number is `9`, the new version is `3.(minor+1).0` - Otherwise, increment patch: `3.x.y` → `3.x.(y+1)` If the version was ALREADY bumped (e.g. you are on a release bran...