From f3fbef64ca809979d3c96d03e8298a1071a06ef3 Mon Sep 17 00:00:00 2001
From: Lukasz Raczylo <lukasz@raczylo.com>
Date: Sat, 9 May 2026 18:19:03 +0100
Subject: [PATCH] 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.
---
 .semver.yaml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/.semver.yaml b/.semver.yaml
index 52e3a8b..bb1f0c8 100644
--- a/.semver.yaml
+++ b/.semver.yaml
@@ -39,5 +39,8 @@ wording:
   minor:
     - "feat"
   major:
-    - "breaking"
+    # 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"