fix(ci): use "release-X.Y" npm tag format for version branches

himself65 · himself65 · commit c8ef9d563bd3 · 2026-03-02T02:33:17.000+09:00
Both "1.4" and "v1.4" are valid SemVer ranges rejected by npm.
Use "release-1.4" format instead.
diff --git a/.claude/rules/release.md b/.claude/rules/release.md
@@ -51,7 +51,7 @@ For maintaining older versions (e.g., v1.3.x while v1.4.x is latest):
 
 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 `v1.4`)
+   (e.g., `v1.4.x` publishes with tag `release-1.4`)
 
 ## Notes
 
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -61,8 +61,8 @@ jobs:
               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
-              # Prefix with "v" to avoid SemVer range conflict (npm rejects bare "1.4")
-              NPM_TAG="v${BASH_REMATCH[1]}"
+              # 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 or a version branch (v*.*.x)."
               echo "::error ::Releases must be on the main branch or a version branch (v*.*.x)."
