Enhance automation: Add auto-versioning and release creation to CI/CD

Author: Maxim Titovich

.github/workflows/publish.yml

@@ -10,12 +10,24 @@ on:
       - 'build/**'
   release:
     types: [created]
+  workflow_dispatch:
+    inputs:
+      force_publish:
+        description: 'Force publish even if version exists'
+        required: false
+        type: boolean
+        default: false
 
 jobs:
   publish:
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      packages: write
     steps:
     - uses: actions/checkout@v3
+      with:
+        fetch-depth: 0
 
     - name: Use Node.js
       uses: actions/setup-node@v3
@@ -24,6 +36,11 @@ jobs:
         cache: 'npm'
         registry-url: 'https://registry.npmjs.org'
 
+    - name: Setup Git
+      run: |
+        git config user.name "GitHub Actions Bot"
+        git config user.email "[email protected]"
+    
     - name: Install dependencies
       run: npm ci
 
@@ -52,9 +69,54 @@ jobs:
           echo "Version ${{ steps.extract_version.outputs.version }} doesn't exist yet"
         fi
       continue-on-error: true
+    
+    # Auto bump version if it already exists and force_publish is true or triggered by push
+    - name: Auto bump version if needed
+      id: auto_bump
+      if: |
+        (steps.version_check.outputs.exists == 'true') && 
+        ((github.event_name == 'push') || (github.event_name == 'workflow_dispatch' && inputs.force_publish))
+      run: |
+        echo "Auto-bumping version because version ${{ steps.extract_version.outputs.version }} already exists"
+        npm version patch -m "Auto bump version to %s [skip ci]"
+        echo "new_version=$(node -p "require('./package.json').version")" >> $GITHUB_OUTPUT
+    
+    # Get final version to use
+    - name: Determine final version
+      id: final_version
+      run: |
+        if [[ "${{ steps.auto_bump.outputs.new_version }}" != "" ]]; then
+          echo "version=${{ steps.auto_bump.outputs.new_version }}" >> $GITHUB_OUTPUT
+          echo "Using auto-bumped version: ${{ steps.auto_bump.outputs.new_version }}"
+        else
+          echo "version=${{ steps.extract_version.outputs.version }}" >> $GITHUB_OUTPUT
+          echo "Using original version: ${{ steps.extract_version.outputs.version }}"
+        fi
+    
+    # Push changes if version was bumped
+    - name: Push changes if version was bumped
+      if: steps.auto_bump.outputs.new_version != ''
+      run: |
+        git push
+        git push --tags
+    
+    # Create GitHub release if version was bumped or if the version doesn't exist (for manual releases)
+    - name: Create GitHub Release
+      if: |
+        (steps.auto_bump.outputs.new_version != '') || 
+        (steps.version_check.outputs.exists == 'false')
+      uses: softprops/action-gh-release@v1
+      with:
+        tag_name: v${{ steps.final_version.outputs.version }}
+        name: Release v${{ steps.final_version.outputs.version }}
+        generate_release_notes: true
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
     - name: Publish to npm
-      if: steps.version_check.outputs.exists != 'true'
+      if: |
+        (steps.version_check.outputs.exists == 'false') || 
+        (steps.auto_bump.outputs.new_version != '')
       run: npm publish
       env:
         NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} 

README.md

@@ -346,17 +346,24 @@ You can see the workflow details in `.github/workflows/ci.yml`.
 The publishing workflow runs when:
 - A change is pushed to the main branch that modifies `package.json` or source code
 - A new GitHub release is created
+- Manually triggered via GitHub Actions interface
 
 It performs the following steps:
 1. Runs all checks and builds the package
 2. Extracts the package version from package.json
 3. Checks if that version already exists on npm
-4. If the version is new, publishes the package to npm
+4. If the version exists, automatically bumps the patch version
+5. Creates a GitHub release for the new version
+6. Publishes the package to npm
 
 To use this workflow, you need to:
 1. Add an `NPM_TOKEN` secret to your GitHub repository settings
-2. Increase the version number in package.json when ready to publish
-3. Push to the main branch or create a new GitHub release
+2. Either:
+   - Push changes to the main branch (auto-versioning will handle the rest)
+   - Manually trigger the workflow from the Actions tab
+   - Create a GitHub release
+
+The workflow supports automatic version bumping when a version conflict is detected, making continuous delivery seamless.
 
 You can see the workflow details in `.github/workflows/publish.yml`.