Update version detection logic and documentation for accurate version bumping

Author: ChristophShyper

.github/VERSION-DETECTION.md

@@ -4,7 +4,7 @@ This file demonstrates how the automated version detection works with different
 
 ## Branch-Based Version Detection
 
-### ✅ Major Version Bump (v0.10.2 → v0.11.0)
+### ✅ Minor Version Bump (v0.10.2 → v0.11.0)
 **Trigger**: Merging from `feat*` branches
 
 ```bash
@@ -16,10 +16,10 @@ git commit -m "add user profile management"
 git push origin feat/new-user-authentication
 
 # Create PR and merge to master
-# Result: Automatic major version bump v0.10.2 → v0.11.0
+# Result: Automatic minor version bump v0.10.2 → v0.11.0
 ```
 
-### ✅ Minor Version Bump (v0.10.2 → v0.10.3)  
+### ✅ Patch Version Bump (v0.10.2 → v0.10.3)  
 **Trigger**: Merging from any other branch
 
 ```bash
@@ -46,24 +46,25 @@ The system checks in this order:
 1. **Feature branches** (highest priority)
    - Checks merged branch names for `feat*` pattern
    - Also checks commit messages for `feat:` prefix
-   - Results in major version bump
+   - Results in minor version bump (Y)
 
 2. **Everything else** (default)
    - All other branch merges and commits
-   - Results in minor version bump
+   - Results in patch version bump (Z)
 
 ## Example Scenarios
 
 | Branch Name | Commit Message | Version Change | Reason |
 |-------------|----------------|----------------|---------|
-| `feat/auth` | "add login system" | v0.10.2 → v0.11.0 | feat branch |
-| `fix/bug` | "fix: resolve crash" | v0.10.2 → v0.10.3 | non-feat branch |
-| `docs/readme` | "docs: update guide" | v0.10.2 → v0.10.3 | non-feat branch |
-| `fix/bug` | "feat: add new feature" | v0.10.2 → v0.11.0 | feat in commit |
-| `refactor/code` | "refactor: improve structure" | v0.10.2 → v0.10.3 | non-feat branch |
+| `feat/auth` | "add login system" | v0.10.2 → v0.11.0 | feat branch (minor) |
+| `fix/bug` | "fix: resolve crash" | v0.10.2 → v0.10.3 | non-feat branch (patch) |
+| `docs/readme` | "docs: update guide" | v0.10.2 → v0.10.3 | non-feat branch (patch) |
+| `fix/bug` | "feat: add new feature" | v0.10.2 → v0.11.0 | feat in commit (minor) |
+| `refactor/code` | "refactor: improve structure" | v0.10.2 → v0.10.3 | non-feat branch (patch) |
 
 This ensures that:
-- ✅ New features always increment major version (minor number)
-- ✅ Bug fixes and other changes increment minor version (patch number)
+- ✅ New features always increment minor version (Y number)
+- ✅ Bug fixes and other changes increment patch version (Z number)
+- ✅ Major version (X) is only incremented manually
 - ✅ Documentation and dependency updates don't trigger releases
 - ✅ No manual version management needed

.github/workflows/AUTO-RELEASE.yml

@@ -10,9 +10,10 @@ on:
       release_type:
         description: 'Type of release'
         required: true
-        default: 'minor'
+        default: 'patch'
         type: choice
         options:
+        - patch
         - minor
         - major
 

.github/workflows/AUTO-VERSION.yml

@@ -81,15 +81,15 @@ jobs:
           # Determine version type
           VERSION_TYPE="${{ github.event.inputs.release_type }}"
           if [ "$VERSION_TYPE" = "auto" ] || [ -z "$VERSION_TYPE" ]; then
-            # Check for feat branches first (major version bump)
+            # Check for feat branches first (minor version bump - Y)
             if echo "$MERGED_BRANCHES" | grep -i "^feat\|/feat"; then
-              VERSION_TYPE="major"
+              VERSION_TYPE="minor"
             # Check for feat in commit messages as fallback
             elif echo "$COMMIT_MESSAGES" | grep -i "^feat\|feat:"; then
-              VERSION_TYPE="major"
-            # Everything else is minor
-            else
               VERSION_TYPE="minor"
+            # Everything else is patch (Z)
+            else
+              VERSION_TYPE="patch"
             fi
           fi
           
@@ -104,10 +104,10 @@ jobs:
           
           case $VERSION_TYPE in
             major)
-              NEW_VERSION="v${MAJOR}.$((MINOR + 1)).0"
+              NEW_VERSION="v$((MAJOR + 1)).0.0"
               ;;
             minor)
-              NEW_VERSION="v${MAJOR}.${MINOR}.$((PATCH + 1))"
+              NEW_VERSION="v${MAJOR}.$((MINOR + 1)).0"
               ;;
             patch)
               NEW_VERSION="v${MAJOR}.${MINOR}.$((PATCH + 1))"
@@ -173,8 +173,9 @@ jobs:
             4. 🧹 Release branch automatically cleaned up
             
             🔍 Version Detection Logic
-            - `major`: Merges from feat* branches or feat: in commits (v0.10.2 → v0.11.0)
-            - `minor`: All other changes (v0.10.2 → v0.10.3)
+            - `major`: Manual releases only (v0.10.2 → v1.0.0)
+            - `minor`: Merges from feat* branches or feat: in commits (v0.10.2 → v0.11.0)
+            - `patch`: All other changes (v0.10.2 → v0.10.3)
             
             **This PR is safe to auto-merge - it only contains version updates.**
             

README.md

@@ -245,12 +245,12 @@ You can also trigger releases manually via GitHub Actions UI:
 To help with automatic version detection, use these patterns:
 
 ```bash
-# Minor version (v0.10.2 → v0.10.3) - Most common
+# Patch version (v0.10.2 → v0.10.3) - Most common
 git commit -m "fix: resolve issue with force push"
 git commit -m "docs: update README"
 git commit -m "refactor: improve code structure"
 
-# Major version (v0.10.2 → v0.11.0) - Feature branches or feat commits
+# Minor version (v0.10.2 → v0.11.0) - Feature branches or feat commits
 # Create feature branch:
 git checkout -b feat/new-functionality
 git commit -m "add new amend functionality"
@@ -262,20 +262,25 @@ git commit -m "feat: add new amend functionality"
 
 The system prioritizes **branch names** for version detection:
 
-- **`feat/*` branches** → **Major version bump** (v0.10.2 → v0.11.0)
+- **`feat/*` branches** → **Minor version bump** (v0.10.2 → v0.11.0)
   ```bash
   git checkout -b feat/new-feature
-  # When merged to master → major version bump
+  # When merged to master → minor version bump
   ```
 
-- **Other branches** → **Minor version bump** (v0.10.2 → v0.10.3)
+- **Other branches** → **Patch version bump** (v0.10.2 → v0.10.3)
   ```bash
   git checkout -b fix/bug-fix
   git checkout -b docs/update-readme
   git checkout -b refactor/cleanup
-  # When merged to master → minor version bump
+  # When merged to master → patch version bump
   ```
 
+**🔢 Major Version Handling**
+- **Major versions** (X in vX.Y.Z) are only incremented manually
+- Use **Actions** → **Auto-Release** → **Run workflow** and select "major"
+- This is reserved for breaking changes or significant API changes
+
 ### 🧪 Testing with Test Branches
 
 For testing changes before they reach master: