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

himself65 · himself65 · commit 41d6c31553a2 · 2026-03-02T02:22:32.000+09:00
Version branches like v1.4.x now publish with a version-based npm tag
(e.g., `1.4`) instead of `latest`, so they don't override the current
main release.
diff --git a/.claude/rules/release.md b/.claude/rules/release.md
@@ -49,8 +49,9 @@ The release workflow will publish to npm with the `beta` tag.
 
 For maintaining older versions (e.g., v1.3.x while v1.4.x is latest):
 
-1. Create a version branch named `v1.3.x-latest`
-2. Tags pushed from this branch will also receive the `latest` npm tag
+1. Create a version branch named `v1.3.x` (or `v1.4.x`, etc.)
+2. Tags pushed from this branch will receive the version as the npm tag
+   (e.g., `v1.4.x` publishes with tag `1.4`)
 
 ## Notes
 
@@ -66,5 +67,5 @@ For maintaining older versions (e.g., v1.3.x while v1.4.x is latest):
 * All releases are triggered by pushing tags matching `v*`
 * The CI determines the npm tag based on:
   * Pre-release suffix in tag name (canary, beta, rc, next)
-  * Whether the commit is on `main` or a version branch (`v*.*.x-latest`)
+  * Whether the commit is on `main` or a version branch (`v*.*.x`)
 * Always ensure CI is green before creating release tags
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -55,16 +55,16 @@ jobs:
           else
             # Check if the commit is on the main branch or a version branch
             git fetch origin main
-            CURRENT_BRANCH=$(git branch -r --contains "$GITHUB_SHA" | grep -E 'origin/(main|v[0-9]+\.[0-9]+\.x-latest)' | head -1 | sed 's/.*origin\///')
+            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-latest$ ]]; then
-              # For version branches like v1.3.x-latest, v1.4.x-latest, use "latest" tag
-              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
+              NPM_TAG="${BASH_REMATCH[1]}"
             else
-              echo "The tagged commit is not on the main branch or a version branch (v*.*.x-latest)."
-              echo "::error ::Releases with the 'latest' npm tag must be on the main branch or a version 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
