Files
go-telegram/.semver.yaml
T
lukaszraczylo 5a27b53f30 fix(release): remove tag_prefixes — it filtered all v* tags out
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.
2026-05-09 18:30:46 +01:00

48 lines
1.4 KiB
YAML

# Configuration for lukaszraczylo/semver-generator.
# Reference: https://github.com/lukaszraczylo/semver-generator
#
# Word matching is fuzzy + case-insensitive. The keywords below mirror
# Conventional Commits prefixes used in this repo's git history.
version: 1
# Respect existing v* tags as the version baseline. semver-generator finds
# the highest existing tag and bumps from there.
force:
existing: true
# Skip merge commits and machine-generated traffic that would otherwise
# spuriously bump the version.
blacklist:
- "Merge branch"
- "Merge pull request"
- "Merge remote-tracking branch"
- "go mod tidy"
# 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:
- "fix"
- "chore"
- "docs"
- "test"
- "style"
- "refactor"
- "build"
- "ci"
- "perf"
minor:
- "feat"
major:
# Match only the canonical Conventional Commits trailer. The bare
# word "breaking" is too greedy under semver-generator's fuzzy match —
# it triggers on substrings like "breaking-value drift" inside a
# commit body and wrongly produces a major bump.
- "BREAKING CHANGE"