fix(ci): use version-specific npm tag for version branches

Author: himself65

.github/workflows/release.yml

@@ -45,13 +45,19 @@ jobs:
             # Extract pre-release tag (e.g., beta, rc)
             NPM_TAG=${BASH_REMATCH[1]}
           else
-            # Check if the commit is on the main branch
+            # Check if the commit is on the main branch or a version branch
             git fetch origin main
-            if git merge-base --is-ancestor "$GITHUB_SHA" origin/main; then
+            CURRENT_BRANCH=$(git branch -r --contains "$GITHUB_SHA" | grep -E 'origin/(main|v[0-9]+\.[0-9]+\.x)' | head -1 | sed 's/.*origin\///')
+
+            if [[ "$CURRENT_BRANCH" == "main" ]]; then
               NPM_TAG="latest"
+            elif [[ "$CURRENT_BRANCH" =~ ^v([0-9]+\.[0-9]+)\.x$ ]]; then
+              # For version branches like v1.3.x, v1.4.x, use the version as npm tag
+              # Use "release-X.Y" format to avoid SemVer range conflict (npm rejects "1.4" and "v1.4")
+              NPM_TAG="release-${BASH_REMATCH[1]}"
             else
-              echo "The tagged commit is not on the main branch."
-              echo "::error ::Releases with the 'latest' npm tag must be on the main branch."
+              echo "The tagged commit is not on the main branch or a version branch (v*.*.x)."
+              echo "::error ::Releases must be on the main branch or a version branch (v*.*.x)."
               exit 1
             fi
           fi