Skip to content

ci(dependabot): switch to security-only mode#327

Merged
robgruen merged 4 commits into
mainfrom
dev/talzacc/dependabot-security-only
Jun 2, 2026
Merged

ci(dependabot): switch to security-only mode#327
robgruen merged 4 commits into
mainfrom
dev/talzacc/dependabot-security-only

Conversation

@TalZaccai
Copy link
Copy Markdown
Contributor

@TalZaccai TalZaccai commented Jun 2, 2026

Why

Last week's first scheduled Dependabot run produced 5 PRs (#322 #323 #324 #325 #326): one grouped minor/patch bump plus 4 ungrouped majors. We want zero routine version-update PRs — only security-update PRs.

What this does

Sets open-pull-requests-limit: 0 on each ecosystem block. Per GitHub docs this disables routine version-update PRs while keeping the ecosystem registered so security-update PRs still flow when alerts fire. The applies-to: security-updates grouping rules are preserved so security PRs still consolidate.

Followup

The 4 noisy major PRs (#322 #323 #324 #325 #326) and 2 stale Jan PRs (#314 #317) were already closed. Future routine bumps will need to be made manually (or via a separate workflow); only security alerts will auto-PR.

The previous config opened weekly version-update PRs as well as
security-update PRs. The routine weekly PRs caused major-version churn
(actions/checkout 3->6, Microsoft.SourceLink.GitHub 8->10, etc.) that we
do not want surfaced automatically.

Setting open-pull-requests-limit: 0 on each ecosystem block disables
version-update PRs while keeping the ecosystem registered so
security-update PRs still flow when alerts fire. The security-update
grouping rules are preserved.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Previous revision of this branch set open-pull-requests-limit: 0 to
disable all routine version-update PRs. Per follow-up review we want a
single weekly grouped PR per ecosystem covering majors + minors + patches
instead -- easier to review at a glance than many small PRs.

- Drop open-pull-requests-limit: 0 (let routine PRs flow again)
- Add nuget-all / github-actions-all groups that match every package and
  every update-type (major, minor, patch) -- collapses everything into
  one PR per ecosystem per weekly run.
- Keep the security-updates groups as separate PRs so security work
  isn't buried in routine churn.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@TalZaccai TalZaccai changed the title ci(dependabot): switch to security-only mode ci(dependabot): bundle all routine updates into one PR per ecosystem Jun 2, 2026
@TalZaccai TalZaccai changed the title ci(dependabot): bundle all routine updates into one PR per ecosystem ci(dependabot): switch to security-only mode Jun 2, 2026
Per rubber-duck review:

1. update-types: [minor, patch] is a SemVer-level filter, not an advisory
   severity filter. The earlier comment said "major security bumps fall
   through ungrouped" which conflated SemVer-major with high/critical
   severity. A critical CVE patched by a SemVer-patch bump IS grouped;
   a low CVE requiring a SemVer-major bump is not. Reworded the comments
   to make that explicit.

2. Added a header note listing the repo-level Settings > Code security
   toggles this config depends on (Dependency graph, Dependabot alerts,
   Dependabot security updates, Grouped security updates).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@robgruen robgruen added this pull request to the merge queue Jun 2, 2026
Merged via the queue into main with commit cd53a10 Jun 2, 2026
7 of 8 checks passed
@robgruen robgruen deleted the dev/talzacc/dependabot-security-only branch June 2, 2026 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants