chore(ci): group dependabot security updates per ecosystem - #184
Merged
Merged
Conversation
Security updates arrived one pull request per advisory, because `applies-to` defaults to version updates and the existing groups relied on that implicitly. Each ecosystem now has a security-updates group alongside it. The npm group is deliberately scoped to minor and patch, so without a second group a security fix in a new major would never be grouped at all.
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
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.
Part of the same cleanup as relaticle/custom-fields#217. This repository's workflows are already clean under zizmor, so only the Dependabot config changes.
applies-todefaults toversion-updates, and both existing groups relied on that implicitly. Security updates were therefore ungrouped and arrived one pull request per advisory.The npm group matters more than the others here: it is scoped to
minorandpatch, so a security fix that only exists in a new major was outside every group.Also done outside this PR
allow_auto_mergewas off at the repo level, soauto-merge.ymlcould never merge a Dependabot PR. Now enabled. #172 is waiting on exactly that.Caveat worth deciding separately: a merge enabled with
GITHUB_TOKENdoes not triggeron: pushworkflows, anddeploy-docs.ymlison: pushwithpaths: docs/**. Auto-merged docs bumps would stop redeploying the docs site until that uses a GitHub App token or a scheduled redeploy.