Skip to content

chore(dependabot): group routine and security update PRs#319

Merged
robgruen merged 3 commits into
mainfrom
dev/talzacc/dependabot-grouping
Jun 2, 2026
Merged

chore(dependabot): group routine and security update PRs#319
robgruen merged 3 commits into
mainfrom
dev/talzacc/dependabot-grouping

Conversation

@TalZaccai
Copy link
Copy Markdown
Contributor

Change

Add Dependabot grouping rules to the existing nuget ecosystem (and add coverage for github-actions, which wasn't previously declared) so that multiple updates in a given run collapse into a single PR. Routine version updates and security-advisory-triggered updates are grouped separately (via applies-to: security-updates) so security PRs can be prioritised on their own.

Major-version bumps continue to open one PR per package so reviewers can evaluate them individually, and the existing System.* / Microsoft.Extensions.* / Microsoft.Bcl.* major-version ignore rules remain in effect.

Status

This repo currently has 0 open Dependabot alerts, so this change is preventive — it ensures that when alerts do accumulate, they arrive as a single triagable PR rather than many.

Add grouping rules to the existing nuget and (new) github-actions
ecosystems so that multiple updates in a given run collapse into a
single PR, with security-advisory-triggered updates grouped separately
so they can be prioritised on their own.

Major-version bumps continue to open one PR per package so reviewers
have a chance to evaluate them individually (and the existing
System.* / Microsoft.Extensions.* / Microsoft.Bcl.* major-version
ignore rules remain in effect).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the repository’s Dependabot configuration to reduce update PR noise by grouping routine dependency updates and separating security-triggered updates into their own grouped PRs, and it adds Dependabot coverage for the github-actions ecosystem.

Changes:

  • Add grouping rules for NuGet updates to combine minor/patch updates into a single PR per run.
  • Add a separate NuGet group for security updates via applies-to: security-updates.
  • Add a new github-actions Dependabot ecosystem entry, including grouped routine and security updates.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/dependabot.yml
Comment thread .github/dependabot.yml
…r/patch

Addresses Copilot review feedback on #319: the nuget-security and both github-actions groups previously matched all version updates, which would collapse major-version bumps into the grouped PR. The PR description (and the comment above the nuget groups) promised major bumps would fall through as one-PR-per-package, but only the routine nuget group enforced that.

Adds update-types: [minor, patch] to nuget-security, github-actions, and github-actions-security groups so major bumps remain individual PRs and can be reviewed for breaking-change notes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
TalZaccai added a commit to microsoft/TypeChat that referenced this pull request Jun 2, 2026
…/patch

Same fix applied to microsoft/typechat.net#319: groups without update-types collapse major-version bumps into the grouped PR, which defeats the goal of keeping majors as one-PR-per-package for breaking-change review.

Constrains npm-security, pip-security, devcontainers, github-actions, and github-actions-security groups to [minor, patch]. The npm-production, npm-development, and pip-all groups were already correctly constrained.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@TalZaccai TalZaccai requested a review from robgruen June 2, 2026 03:31
TalZaccai added a commit to microsoft/TypeChat that referenced this pull request Jun 2, 2026
* chore(dependabot): add npm/pip ecosystems and group updates

The existing dependabot.yml only declared the devcontainers and
github-actions ecosystems, leaving npm and pip completely unmanaged.
All open security alerts in this repo (currently 9, all under
typescript/package-lock.json) target ecosystems Dependabot wasn't
watching, so no update PRs have ever been opened for them.

This change:

* Adds npm coverage for /typescript, /typescript/examples/*, and /site
* Adds pip coverage for /python (pyproject.toml)
* Adds grouping rules across all ecosystems so multiple alerts in a
  given run collapse into a single PR (separately for routine
  version updates vs security-advisory-triggered updates, so security
  PRs can be prioritised on their own).

Major-version bumps continue to open one PR per package so reviewers
have a chance to evaluate them individually.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* chore(dependabot): constrain all security & catch-all groups to minor/patch

Same fix applied to microsoft/typechat.net#319: groups without update-types collapse major-version bumps into the grouped PR, which defeats the goal of keeping majors as one-PR-per-package for breaking-change review.

Constrains npm-security, pip-security, devcontainers, github-actions, and github-actions-security groups to [minor, patch]. The npm-production, npm-development, and pip-all groups were already correctly constrained.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* chore(dependabot): tighten header comment

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Same fix applied to microsoft/TypeChat#338 from @robgruen's review: the default 'To get started...' header was the auto-generated template and no longer describes what's in the file. Replaced with a header that documents the routine/security/major-bump grouping policy this config actually applies.

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 e4cccca Jun 2, 2026
7 of 8 checks passed
@robgruen robgruen deleted the dev/talzacc/dependabot-grouping branch June 2, 2026 04:33
TalZaccai added a commit that referenced this pull request Jun 2, 2026
Resolves conflicts from main commits #314 (Microsoft.Extensions.Configuration.Binder
10.0.1 -> 10.0.2) and #319 (Dependabot grouping config).

Conflict resolution:
- 3 csproj files (examples/typechat.examplesLib, src/typechat.meai,
  src/typechat.sk): kept ours (version-less PackageReferences, as
  required by CPM).
- Directory.Packages.props: bumped Microsoft.Extensions.Configuration.Binder
  PackageVersion from 10.0.1 to 10.0.2 to absorb the #314 change centrally
  so all consumers pick it up via CPM.
- .github/dependabot.yml, OpenAIConfig.cs, integration_tests.yml: merged
  in cleanly from main without conflict.

Validation:
- dotnet restore: clean, 0 NU190x warnings
- dotnet build /warnaserror: 0 warnings, 0 errors
- dotnet test tests/TypeChat.UnitTests: 154/154 passed

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

3 participants