ci: put the deps scope in the Dependabot commit prefix - #263
Merged
Conversation
include: scope did not resolve a dependency type for these ecosystems, so recreated PRs landed as "chore: Bump ..." with no scope. Spelling the scope into prefix and prefix-development produces chore(deps) unconditionally.
fuzzzerd
enabled auto-merge (squash)
August 19, 2026 22:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Follow-up to #260. That change pinned
prefix: chorewithinclude: "scope", but the recreated group PRs (#261, #262) came back aschore: Bump the nlog group with 2 updates— the(deps)scope was never added.include: "scope"derives the scope from dependency-type resolution, which produces nothing for these ecosystems. Spelling the scope directly intoprefixandprefix-developmentmakes the title deterministic:includeis dropped, since keeping it alongside a prefix that already carries a scope risks emitting it twice.