From 77ab5a19babe4b373fe802c336f701b29b725fda Mon Sep 17 00:00:00 2001 From: Changsik00 Date: Sun, 17 May 2026 11:26:47 +0900 Subject: [PATCH] ci(release): restrict tag trigger to semver-only MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous 'v*' pattern would trigger this workflow on moving major tags (v1, v2 …) that Action consumers track via 'uses: Changsik00/node-settings@v1'. Re-publishing the same npm version from a moved major tag would fail noisily ('cannot publish over existing version'), and the GitHub Release that softprops creates would shadow the real semver release. Restrict to 'v[0-9]+.[0-9]+.[0-9]+' so only true releases publish, and movable major tags can be re-pointed without side effects. --- .github/workflows/release.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index cdacaaa..25fa853 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -19,7 +19,10 @@ name: Release on: push: tags: - - 'v*' + # Semver tags only (vMAJOR.MINOR.PATCH). Moving major tags like + # `v1` — used by Action consumers writing `uses: …@v1` to track + # the latest v1.x.y — must NOT trigger another npm publish. + - 'v[0-9]+.[0-9]+.[0-9]+' workflow_dispatch: inputs: tag: