Files
go-telegram/.semver.yaml
T
lukaszraczylo f3fbef64ca chore(release): require canonical BREAKING CHANGE trailer for major
The bare 'breaking' major-bump keyword was matching substrings like
'breaking-value drift' in commit bodies, producing surprise major
bumps. Restrict the major trigger to the canonical Conventional
Commits trailer only.
2026-05-09 18:19:03 +01:00

47 lines
1.3 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"
# 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-"
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"