From 5598cc725734f70cc49e3e547a7a2a14ab62427a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?An=C4=B1lcan=20=C3=87ak=C4=B1r?= Date: Sun, 30 Aug 2026 14:46:14 +0300 Subject: [PATCH] fix(deps): one scope per commit message, not two `include: scope` makes Dependabot append its own `(deps)` to whatever prefix it is given, so a prefix that already carries a scope produces the doubled shape. The first bump under the new config landed as `chore(backend-deps)(deps): bump ...`, which is not a conventional commit and not what the buckets with a plain `chore` prefix produce. Dropped `include: scope` from every bucket whose prefix already names its scope, and left it on the ones whose prefix is bare. wind's own config warned about exactly this in its header comment and then did it anyway in the example bucket. --- .github/dependabot.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index dfeacca..f813cec 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -73,7 +73,9 @@ updates: - anilcancakir commit-message: prefix: chore(backend-deps) - include: scope + # No `include: scope` here: Dependabot appends its own `(deps)` when that + # is set, and this prefix already carries a scope. The pair produced + # `chore(backend-deps)(deps): ...` on the first bump. groups: backend-minor-and-patch: patterns: