From 5a27b53f30217ae3e880542fc9e5ac69258d2a7e Mon Sep 17 00:00:00 2001 From: Lukasz Raczylo Date: Sat, 9 May 2026 18:30:46 +0100 Subject: [PATCH] =?UTF-8?q?fix(release):=20remove=20tag=5Fprefixes=20?= =?UTF-8?q?=E2=80=94=20it=20filtered=20all=20v*=20tags=20out?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Setting tag_prefixes: ['bot-api-'] caused semver-generator to ignore every tag without that prefix, including the v0.x.y / v1.x.y release tags. With no parseable existing version, it restarted numbering at zero and produced v0.0.4 as a 'next' version after v1.1.1 — a regression Go modules would never serve. The bot-api-vX.Y marker is set by a separate workflow step; semver- generator does not need to see it. --- .semver.yaml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/.semver.yaml b/.semver.yaml index bb1f0c8..1040edf 100644 --- a/.semver.yaml +++ b/.semver.yaml @@ -19,11 +19,12 @@ blacklist: - "Merge remote-tracking branch" - "go mod tidy" -# Strip the auto-generated bot-api-vX.Y tag prefix when scanning existing -# tags — those are markers that point at library releases, not version -# sources themselves. -tag_prefixes: - - "bot-api-" +# NOTE: do not configure tag_prefixes here. The action's behaviour with +# that option present is to FILTER tags down to those matching the +# listed prefixes — meaning v0.x.y / v1.x.y tags get ignored and version +# numbering restarts from zero. The bot-api-vX.Y tag is created by a +# separate workflow step and does not need to participate in version +# selection. wording: patch: