release-version-bump-auto

Release Version Bump

Critical Rules

• Must validate version bump against change analysis
• Must block releases when breaking changes exist but non-major version is requested
• Must provide clear error messages for version mismatches
• Must offer force continue options for version mismatches
• Must calculate new version numbers based on semantic versioning
• Must handle custom version inputs

filters:

• type: content pattern: "(release|version|tag|bump|publish|deploy).*(create|make|generate|prepare|ready)"
• type: git_branch pattern: "^(?!main$|master$).*$"
• type: event pattern: "chat_start|chat_response"

actions:

• type: generate content: |

  🔄 Version Bump Process

  I'll help you choose and validate the appropriate version bump for your release.

  1. Prompt User for Version Bump (if not specified):

     if [ -z "$VERSION_BUMP" ]; then
       # Calculate potential new versions
       MAJOR_VERSION=$(echo $CURRENT_VERSION | awk -F. '{print $1+1 ".0.0"}')
       MINOR_VERSION=$(echo $CURRENT_VERSION | awk -F. '{print $1 "." $2+1 ".0"}')
       PATCH_VERSION=$(echo $CURRENT_VERSION | awk -F. '{print $1 "." $2 "." $3+1}')
       
       echo "Choose your version bump:"
       echo "1) Major version: $CURRENT_VERSION → $MAJOR_VERSION (breaking changes)"
       echo "2) Minor version: $CURRENT_VERSION → $MINOR_VERSION (new features)"
       echo "3) Patch version: $CURRENT_VERSION → $PATCH_VERSION (bug fixes)"
       echo "4) Custom version"
       
       # Wait for user input
       read -p "Enter your choice (1-4): " USER_CHOICE
       
       case $USER_CHOICE in
         1) VERSION_BUMP="major" ;;
         2) VERSION_BUMP="minor" ;;
         3) VERSION_BUMP="patch" ;;
         4) 
           read -p "Enter custom version: " CUSTOM_VERSION
           VERSION_BUMP="custom"
           ;;
       esac
     fi