chore(dependabot): add npm/pip ecosystems and group updates#338
Merged
Conversation
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>
Contributor
There was a problem hiding this comment.
Pull request overview
Expands the Dependabot configuration to cover npm (typescript library, examples, site) and pip (python) ecosystems that previously had no Dependabot coverage, and introduces grouping rules so multiple updates collapse into single PRs while security updates remain a separate group.
Changes:
- Add npm ecosystem entry covering
/typescript,/typescript/examples/*, and/sitewith production/development/security groups. - Add pip ecosystem entry covering
/pythonwith general and security groups. - Add grouping rules to existing
devcontainersandgithub-actionsentries (the latter also separating security updates).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…/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>
robgruen
approved these changes
Jun 2, 2026
TalZaccai
added a commit
that referenced
this pull request
Jun 2, 2026
Addresses review feedback on #338 from @robgruen: the default 'To get started...' header was the auto-generated template from when the file was first created and no longer matches the actual content (which now defines grouping policy across 4 ecosystems). Replaces it with a header that documents the routine/security/major-bump grouping rationale that's actually applied throughout the file. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
TalZaccai
force-pushed
the
dev/talzacc/dependabot-expand-and-group
branch
from
140ea55 to
1b66d3b
Compare
TalZaccai
added a commit
to microsoft/typechat.net
that referenced
this pull request
Jun 2, 2026
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>
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.
Problem
The existing
.github/dependabot.ymlonly declared thedevcontainersandgithub-actionsecosystems. All 9 currently-open security alerts in this repo targettypescript/package-lock.json(tar,qs,minimatch,@tootallnate/once) — a manifest under an ecosystem Dependabot wasn't watching — so no update PRs have ever been opened for any of them. The Python tree (/python/pyproject.toml) is similarly uncovered.Change
npmcoverage for/typescript,/typescript/examples/*, and/sitepipcoverage for/pythonapplies-to: security-updates) so security PRs can be prioritised on their own.Expected outcome
After merge, the next Dependabot run (weekly Monday) should open at most one grouped npm-security PR covering the existing 9 alerts.