Skip to content

ci: group security updates the way version updates are grouped #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AndresSaa merged 1 commit into from
Aug 8, 2026
Merged

ci: group security updates the way version updates are grouped #46

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,18 @@ updates:
schedule:
interval: "weekly"
groups:
# Two groups with identical membership, because `applies-to` defaults to
# version updates: without the second one, security advisories bypass
# grouping entirely and arrive as one pull request per package. A single
# mermaid-cli upgrade landed as two that way. Both patterns take
# everything — a package with zero runtime dependencies has nothing here
# but dev tooling.
dev-dependencies:
applies-to: version-updates
patterns:
- "*"
security-advisories:
applies-to: security-updates
patterns:
- "*"
ignore:
Expand Down