chore(dependabot): group github-actions + docker bumps like npm does#271
Merged
CryptoJones merged 1 commit intoMay 19, 2026
Merged
Conversation
The npm ecosystem already bundles minor+patch dependency bumps into a single weekly PR via a `minor-and-patch` group — keeps the PR queue from fragmenting when several deps tick at once. The github-actions and docker ecosystems didn't have the same group, so every action / base-image patch was landing as its own PR. Add the same group to both, matching the existing pattern. Majors still land as separate PRs because a base-image major bump (node:26 → node:28 etc.) or a checkout-action major can carry a breaking change worth a focused review. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
The npm ecosystem in
.github/dependabot.ymlalready bundles minor+patch dependency bumps into a single weekly PR via aminor-and-patchgroup. The github-actions and docker ecosystems didn't have the same group, so every action / base-image patch landed as its own PR — fragmenting the queue.What changed
Added the same
minor-and-patchgroup to both:github-actions: bundles action patch/minor bumps weekly.docker: bundles base-image patch/minor bumps (node:26-bookworm-slim point releases, postgres:16-alpine point releases).Majors still land as separate PRs in both ecosystems, because a base-image major (node:26 → 28) or a
actions/checkoutmajor can carry a breaking change worth focused review.Test plan
npm run lint && npm test— 760 passing (config-only change).Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/