Summary
Dependabot grouped updates are producing merge commits such as chore(deps)(deps): bump the github-actions group with 5 updates, which Release Please cannot parse as a Conventional Commit.
Evidence
Release Please ran after Dependabot PR #531 merged, but the action log reported:
commit could not be parsed: 27b5bc61... chore(deps)(deps): bump the github-actions group with 5 updates (#531)
error message: Error: unexpected token `(` at 1:12, valid tokens [!, :]
commits: 0
Considering: 0 commits
No commits for path: ., skipping
The current Dependabot configuration sets prefix: "chore(deps)" together with include: "scope", which appears to produce the doubled scope.
Proposed fix
Update Dependabot commit-message configuration so the prefix does not include a scope when include: "scope" is enabled, producing commits like chore(deps): ... instead of chore(deps)(deps): ....
Acceptance criteria
- Dependabot commit-message prefixes are valid Conventional Commit prefixes.
- Grouped Dependabot PR titles/merge commits no longer contain doubled scopes.
- YAML linting passes.
Summary
Dependabot grouped updates are producing merge commits such as
chore(deps)(deps): bump the github-actions group with 5 updates, which Release Please cannot parse as a Conventional Commit.Evidence
Release Please ran after Dependabot PR #531 merged, but the action log reported:
The current Dependabot configuration sets
prefix: "chore(deps)"together withinclude: "scope", which appears to produce the doubled scope.Proposed fix
Update Dependabot commit-message configuration so the prefix does not include a scope when
include: "scope"is enabled, producing commits likechore(deps): ...instead ofchore(deps)(deps): ....Acceptance criteria