Skip to content

Add dependabot to automatically update dependencies #2885

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

Closed
wants to merge 6 commits into from
Closed

Add dependabot to automatically update dependencies #2885

Changes from 4 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f03a4ed
Merge remote-tracking branch 'upstream/main'
olaservo Oct 13, 2025
6ae9f1b
Merge remote-tracking branch 'upstream/main'
olaservo Oct 19, 2025
a30481d
Merge upstream/main into main
olaservo Oct 19, 2025
0af7f3f
Add Dependabot configuration for monorepo with grouped updates
olaservo Oct 19, 2025
85e1a4e
Update .github/dependabot.yml
olaservo Oct 19, 2025
28fb058
Update .github/dependabot.yml
olaservo Oct 19, 2025
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
86 changes: 86 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,86 @@
version: 2
updates:
# Root npm dependencies
- package-ecosystem: "npm"
directory: "/"
schedule:
interval: "weekly"
groups:
npm-dependencies:
Copy link

Copilot AI Oct 19, 2025

Choose a reason for hiding this comment

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

All npm package ecosystems use the same group name 'npm-dependencies', which will result in separate PRs per directory rather than a single grouped PR as described in the PR description. To achieve the stated goal of '1 PR for all npm updates', use a unique group name (e.g., 'all-npm-dependencies') consistently across all npm configurations, or consider Dependabot's repository-level grouping feature if available.

Copilot uses AI. Check for mistakes.
patterns:
- "*"

# TypeScript/Node.js servers
- package-ecosystem: "npm"
directory: "/src/everything"
schedule:
interval: "weekly"
groups:
npm-dependencies:
Copy link

Copilot AI Oct 19, 2025

Choose a reason for hiding this comment

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

All npm package ecosystems use the same group name 'npm-dependencies', but Dependabot group names must be unique per update configuration. Each directory's npm updates will create separate PRs instead of being consolidated. To group all npm updates into a single PR as described in the PR description, you need to use unique group names or configure a repository-level grouping rule in the Dependabot configuration.

Copilot uses AI. Check for mistakes.
patterns:
- "*"

- package-ecosystem: "npm"
directory: "/src/filesystem"
schedule:
interval: "weekly"
groups:
npm-dependencies:
patterns:
- "*"

- package-ecosystem: "npm"
directory: "/src/memory"
schedule:
interval: "weekly"
groups:
npm-dependencies:
patterns:
- "*"

- package-ecosystem: "npm"
directory: "/src/sequentialthinking"
schedule:
interval: "weekly"
groups:
npm-dependencies:
patterns:
- "*"

Copy link

Copilot AI Oct 19, 2025

Choose a reason for hiding this comment

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

All npm package ecosystems use the same group name 'npm-dependencies', but Dependabot group names must be unique per update configuration. Each directory's npm updates will create separate PRs instead of being consolidated. To group all npm updates into a single PR as described in the PR description, you need to use unique group names or configure a repository-level grouping rule in the Dependabot configuration.

Suggested change
groups:
npm-dependencies:
patterns:
- "*"
# TypeScript/Node.js servers
- package-ecosystem: "npm"
directory: "/src/everything"
schedule:
interval: "weekly"
groups:
npm-dependencies:
patterns:
- "*"
- package-ecosystem: "npm"
directory: "/src/filesystem"
schedule:
interval: "weekly"
groups:
npm-dependencies:
patterns:
- "*"
- package-ecosystem: "npm"
directory: "/src/memory"
schedule:
interval: "weekly"
groups:
npm-dependencies:
patterns:
- "*"
- package-ecosystem: "npm"
directory: "/src/sequentialthinking"
schedule:
interval: "weekly"
groups:
npm-dependencies:
patterns:
- "*"
# TypeScript/Node.js servers
- package-ecosystem: "npm"
directory: "/src/everything"
schedule:
interval: "weekly"
- package-ecosystem: "npm"
directory: "/src/filesystem"
schedule:
interval: "weekly"
- package-ecosystem: "npm"
directory: "/src/memory"
schedule:
interval: "weekly"
- package-ecosystem: "npm"
directory: "/src/sequentialthinking"
schedule:
interval: "weekly"
groups:
npm-dependencies:
patterns:
- "*"
update-types:
- "all"

Copilot uses AI. Check for mistakes.
# Python servers
- package-ecosystem: "pip"
directory: "/src/fetch"
schedule:
interval: "weekly"
groups:
python-dependencies:
Copy link

Copilot AI Oct 19, 2025

Choose a reason for hiding this comment

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

All pip package ecosystems use the same group name 'python-dependencies', but group names must be unique per update configuration. Each Python directory will create separate PRs instead of being consolidated into a single PR as intended. To achieve the grouping strategy described in the PR description, you need unique group names or a repository-level grouping configuration.

Copilot uses AI. Check for mistakes.
patterns:
- "*"

- package-ecosystem: "pip"
directory: "/src/git"
schedule:
interval: "weekly"
groups:
python-dependencies:
Copy link

Copilot AI Oct 19, 2025

Choose a reason for hiding this comment

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

All pip package ecosystems use the same group name 'python-dependencies', but group names must be unique per update configuration. Each Python directory will create separate PRs instead of being consolidated into a single PR as intended. To achieve the grouping strategy described in the PR description, you need unique group names or a repository-level grouping configuration.

Copilot uses AI. Check for mistakes.
patterns:
- "*"

- package-ecosystem: "pip"
directory: "/src/time"
schedule:
interval: "weekly"
groups:
python-dependencies:
patterns:
- "*"

# GitHub Actions
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "weekly"
groups:
github-actions:
patterns:
- "*"