ci(deps): use chore(deps)
prefix for dependabot commits
#12881
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Dependabot's recent automated security updates (#12878, #12879, #12880) (enabled after #12763 (comment)) used the
build(deps)
prefix instead ofchore(deps)
build(deps)
and most were auto-merged before I could change the title).This matches the prefix we normally use for dependency updates (#12850, #12860, etc)
build(deps)
for security updates (??)Modifications
commit-message.prefix: chore(deps)
to allpackage-ecosystem
s independabot.yml
:
after the prefixcommit-message.prefix-development: chore(deps-dev)
topackage-ecosystem: npm
(not supported forgithub-actions
orgomod
)Verification
Matches the GH Docs in https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#commit-message