ci: add grouped Dependabot config + patch-only auto-merge workflow#109
Open
jliounis wants to merge 1 commit into
Open
ci: add grouped Dependabot config + patch-only auto-merge workflow#109jliounis wants to merge 1 commit into
jliounis wants to merge 1 commit into
Conversation
Burns down the current Dependabot alert backlog (6 high / 16 moderate / 1 low at the time of writing) without drowning maintainers in tiny one-dep-at-a-time PRs. .github/dependabot.yml ---------------------- - New file. Configures weekly npm + github-actions updates. - Groups production minor+patch into a single weekly PR. - Groups dev minor+patch into a single weekly PR. - Keeps @modelcontextprotocol/* in its own group so SDK churn doesn't get bundled with unrelated transitive upgrades. - Groups all github-actions bumps together. - open-pull-requests-limit: 10 for npm, 5 for actions. - Conventional-commit prefixes: "deps", "deps-dev", "ci". - Labels: dependencies + javascript / github-actions. .github/workflows/dependabot-automerge.yml ------------------------------------------ - New file. Auto-merges Dependabot PRs that are PATCH-only updates AND pass CI (via `gh pr merge --auto`, which waits for required status checks set by branch protection). - Minor and major bumps explicitly stay open for human review and log why they were skipped. - Uses dependabot/fetch-metadata@v2 to classify update-type. - Permissions are scoped to contents:write and pull-requests:write on PRs opened by the dependabot[bot] actor only. What this PR intentionally does NOT do -------------------------------------- - Does not bump @modelcontextprotocol/sdk or other deps directly. The audit found that bumping the SDK does not actually clear the current transitive alerts upstream, so a blind bump is churn without security gain. Let the new grouped Dependabot land the bumps that genuinely move the needle on its first weekly run. - Does not enable required status checks on `main`. That requires repo settings access and should be confirmed with maintainers before turning on (otherwise `--auto` falls back to immediate merge, which we do not want). Pre-merge checklist for maintainers ----------------------------------- 1. Confirm branch protection on `main` requires the `test` job from .github/workflows/test.yml before merge \u2014 this is what makes `gh pr merge --auto` actually wait for CI. 2. Confirm that Dependabot has access to the `dependencies`, `javascript`, and `github-actions` labels (auto-created on first use if not). Tests ----- Both YAML files validate against PyYAML's safe_load. No application code changes; nothing to run via npm test or npm run build.
rbuchmayer-pplx
approved these changes
May 19, 2026
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.
Summary
Burns down the current Dependabot alert backlog (6 high / 16 moderate / 1 low at the time of writing) without drowning maintainers in tiny one-dep-at-a-time PRs.
Adds two files:
.github/dependabot.ymlnpm+github-actionsupdates.production-dependencies: all non-major production minor+patch updatesdevelopment-dependencies: all non-major dev minor+patch updatesmodelcontextprotocol:@modelcontextprotocol/*isolated so SDK churn doesn't get bundled with unrelated transitive upgradesgithub-actions: all action bumps togetherdeps,deps-dev,ci.dependencies,javascript/github-actions..github/workflows/dependabot-automerge.ymlgh pr merge --auto, which waits for required status checks set by branch protection).dependabot/fetch-metadata@v2to classifyupdate-type.contents:write+pull-requests:writeon thedependabot[bot]actor only.What this PR intentionally does NOT do
@modelcontextprotocol/sdkor other deps directly. The audit found that bumping the SDK does not actually clear the current transitive alerts upstream, so a blind bump is churn without security gain. Let the new grouped Dependabot land the bumps that genuinely move the needle on its first weekly run.main. That needs repo-settings access and should be confirmed with maintainers before turning on (otherwisegh pr merge --autofalls back to immediate merge, which we do not want).Pre-merge checklist for maintainers
mainrequires thetestjob from.github/workflows/test.ymlbefore merge — this is what makesgh pr merge --autoactually wait for CI.dependencies,javascript, andgithub-actionslabels (auto-created on first use if missing).Tests
Both YAML files validate against PyYAML's
safe_load. No application code changes;npm testandnpm run buildunaffected.