From f3d9324358ee3b0c10d36183d3f51c17d0095083 Mon Sep 17 00:00:00 2001 From: Alexander van Elsas <58037137+avanelsas@users.noreply.github.com> Date: Tue, 26 May 2026 15:24:18 +0200 Subject: [PATCH] ci(release): restrict core release trigger to v[0-9]* tags The `v*` glob accidentally matched adapter tags that happen to start with 'v', most notably `vue-v0.1.0`. When that tag was pushed during the adapter release sequence, the main `release` workflow queued alongside `release-vue` and would have overwritten the Vue GitHub Release name had it not been cancelled. Tightening the glob to `v[0-9]*` restricts the core release to genuine semver tags (v3.3.0, v3.4.0-rc.1, etc.) and isolates each adapter release to its dedicated workflow. Co-Authored-By: Claude Opus 4.7 (1M context) --- .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 2882cdcf..3c275d8c 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -3,7 +3,10 @@ name: release on: push: tags: - - 'v*' + # Match only core-library semver tags (v1.2.3, v3.3.0-rc.1, …). + # Adapter tags like 'vue-v0.1.0' start with 'v' too — the [0-9] + # guard prevents them from triggering the core release workflow. + - 'v[0-9]*' permissions: contents: write