build: stop grouping Dependabot updates - #25
Merged
Conversation
Grouped runs bundled every bump of the week into a single PR, so one dependency needing a closer look held back the rest. Drop the groups so each dependency gets its own PR and can be reviewed and merged on its own.
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.
Summary
Both Dependabot ecosystems bundled every bump of the week into a single grouped PR. That means one dependency needing a closer look — a major version, say — holds back every other update in the same batch. Dropping the groups gives each dependency its own PR, reviewable and mergeable on its own.
Changes
.github/dependabot.yml: remove thegithub-actionsandpipgroupsblocksSchedule (weekly) and commit-message style (
build(deps): bump ...) are unchanged.