fix tag syntax

Author: DeLaGuardo

.github/workflows/update-major-version-tag.yml

@@ -3,11 +3,11 @@ name: Update Major Version Tag
 on:
   push:
     tags:
-      - 'v[0-9]+.[0-9]+.[0-9]+'
+      - '[0-9]+.[0-9]+.[0-9]+'
   workflow_dispatch:
     inputs:
       tag:
-        description: 'The full version tag to process (e.g., v13.1.0)'
+        description: 'The full version tag to process (e.g., 13.1.0)'
         required: true
         type: string
 
@@ -32,8 +32,8 @@ jobs:
             TAG="${GITHUB_REF#refs/tags/}"
           fi
           echo "tag=$TAG" >> $GITHUB_OUTPUT
-          # Extract major version (e.g., v13 from v13.1.0)
-          MAJOR_TAG=$(echo "$TAG" | sed -E 's/^(v[0-9]+)\..*/\1/')
+          # Extract major version (e.g., 13 from 13.1.0)
+          MAJOR_TAG=$(echo "$TAG" | sed -E 's/^([0-9]+)\..*/\1/')
           echo "major_tag=$MAJOR_TAG" >> $GITHUB_OUTPUT
 
       - name: Update major version tag

README.md

@@ -110,7 +110,7 @@ For more application cases please check [Smoke Test Workflow file](https://githu
 You can reference this action using either:
 
 - **Full version** (e.g., `DeLaGuardo/setup-clojure@13.4.0`) - pins to a specific release
-- **Major version** (e.g., `DeLaGuardo/setup-clojure@v13`) - automatically receives all minor and patch updates within that major version
+- **Major version** (e.g., `DeLaGuardo/setup-clojure@13`) - automatically receives all minor and patch updates within that major version
 
 Using the major version tag is recommended for most users, as it ensures you receive bug fixes and new features without breaking changes.