Skip to content

chore: add dependabot config - #1

Open
yakimoto wants to merge 3 commits into
mainfrom
chore/add-dependabot
Open

chore: add dependabot config#1
yakimoto wants to merge 3 commits into
mainfrom
chore/add-dependabot

Conversation

@yakimoto

@yakimoto yakimoto commented Apr 2, 2026

Copy link
Copy Markdown
Contributor

Adds weekly Dependabot updates for npm dependencies in the example directories that have a package.json (/sdk-quickstart and /adk-hello-agent), with an open PR limit of 10 each.


Summary by cubic

Adds .github/dependabot.yml to enable weekly npm updates for the repo root (/), /sdk-quickstart, and /adk-hello-agent, with a limit of 10 open PRs per directory. Drops /mcp-server-setup; affects only Dependabot PR automation with no runtime or billing impact.

Written for commit 6ef1b7a. Summary will update on new commits.

Review in cubic


Note

Low Risk
Infrastructure-only config for automated dependency PRs in example directories; no application or security-critical code changes.

Overview
Adds .github/dependabot.yml to enable weekly npm dependency updates for the three example projects: sdk-quickstart, mcp-server-setup, and adk-hello-agent.

This keeps example package dependencies current without manual bump PRs.

Reviewed by Cursor Bugbot for commit 796f2b9. Configure here.


Open in Devin Review

Note

Add Dependabot config for weekly npm dependency updates

Adds dependabot.yml to enable weekly npm dependency checks for /, /sdk-quickstart, and /adk-hello-agent, each with a limit of 10 open pull requests.

Macroscope summarized 6ef1b7a.

@coderabbitai

coderabbitai Bot commented Apr 2, 2026

Copy link
Copy Markdown
📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Set up automated weekly dependency updates to maintain package security and stability across the project.

Walkthrough

A new Dependabot configuration file was added to enable automated weekly dependency updates across three npm package directories: /sdk-quickstart, /mcp-server-setup, and /adk-hello-agent. This sets up automated version management for external dependencies in these projects.

Changes

Cohort / File(s) Summary
Dependabot Configuration
.github/dependabot.yml
Added configuration to enable weekly automated dependency updates for npm packages in three separate directories: /sdk-quickstart, /mcp-server-setup, and /adk-hello-agent.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A rabbit's ode to automation

With Dependabot's gentle care,
Dependencies stay fresh and fair,
Weekly updates, smooth and neat,
Three projects march in perfect beat! 📦✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed The description clearly explains the Dependabot configuration and weekly npm dependency updates.
Title check ✅ Passed The title is concise and accurately identifies the main change: adding a Dependabot configuration.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/add-dependabot

Comment @coderabbitai help to get the list of available commands.

@cubic-dev-ai

cubic-dev-ai Bot commented Apr 2, 2026

Copy link
Copy Markdown

This review could not be run because your cubic account has reached a review limit. If you need help restoring access, please contact contact@cubic.dev.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/dependabot.yml:
- Around line 3-14: The dependabot config contains an entry for
/mcp-server-setup but that directory lacks a package.json so Dependabot will
fail; either remove the /mcp-server-setup stanza from .github/dependabot.yml or
add a valid package.json to /mcp-server-setup so npm updates can run, and for
the remaining entries (e.g., /sdk-quickstart and /adk-hello-agent) add an
open-pull-requests-limit setting (open-pull-requests-limit: 10) and optional
grouping rules to batch updates by type to reduce PR noise.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: baeb20f2-5848-416a-957d-7418e6cabc61

📥 Commits

Reviewing files that changed from the base of the PR and between 3f7d3b6 and 796f2b9.

📒 Files selected for processing (1)
  • .github/dependabot.yml
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Seer Code Review
🧰 Additional context used
🔍 Remote MCP

Now let me search for specific considerations about managing multiple npm directories with Dependabot:## Summary of Relevant Context for PR Review

Based on research into Dependabot npm configuration best practices and multi-directory setups, here are the key facts relevant to reviewing this PR:

Configuration Approach Appropriateness

The PR's weekly schedule interval is valid—Dependabot requires the schedule.interval field to be set to daily, weekly, monthly, quarterly, semiannually, yearly, or cron. Weekly checks are a reasonable frequency choice and can be preferred by teams to better organize time and resources for reviewing and addressing version updates.

Multi-Directory npm Configuration

GitHub Dependabot now supports using a directories key to list multiple directories for the same ecosystem configuration in the dependabot.yml file. However, the current configuration approach of creating separate entries for each directory is still valid—developers can still explicitly enumerate configurations for the same ecosystem using the directory key.

Known Considerations for Multiple npm Directories

Potential Issue: When using separate npm directories (particularly with npm workspaces or monorepos), Dependabot may only update the package.json file in individual folders but potentially not sync lockfiles correctly at the workspace root level. This is relevant if /sdk-quickstart, /mcp-server-setup, and /adk-hello-agent are workspace packages or share a root lockfile.

Best Practice for Noise Reduction: For monorepo-style configurations with multiple directories, teams should consider using Dependabot's grouping feature to group updates by dependency name across directories, which creates a single pull request instead of separate ones per directory.

PR Volume Consideration

While weekly schedules work for small projects, enterprise codebases may need more stability through monthly or quarterly checks; batching updates reduces integration overhead. The reviewer should consider whether weekly updates across three directories may create excessive PR volume for the team.

🔇 Additional comments (1)
.github/dependabot.yml (1)

1-2: LGTM: Valid Dependabot v2 configuration.

The version and root structure are correct.

Comment thread .github/dependabot.yml
Comment on lines +3 to +14
- package-ecosystem: npm
directory: /sdk-quickstart
schedule:
interval: weekly
- package-ecosystem: npm
directory: /mcp-server-setup
schedule:
interval: weekly
- package-ecosystem: npm
directory: /adk-hello-agent
schedule:
interval: weekly

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for workspace configuration in package.json files

echo "=== Checking for npm workspace setup ==="

# Check root package.json for workspaces field
if [ -f package.json ]; then
  echo "Root package.json:"
  cat package.json | jq -r 'if .workspaces then "Workspaces: \(.workspaces)" else "No workspaces field" end'
fi

echo -e "\n=== Checking each directory's package.json ==="
for dir in sdk-quickstart mcp-server-setup adk-hello-agent; do
  if [ -f "$dir/package.json" ]; then
    echo -e "\n$dir/package.json exists"
    cat "$dir/package.json" | jq -r '.name // "no name"' | sed 's/^/  Package name: /'
  else
    echo -e "\n$dir/package.json NOT FOUND"
  fi
done

echo -e "\n=== Checking for lockfiles ==="
fd -t f 'package-lock.json|yarn.lock|pnpm-lock.yaml' -x echo "Found: {}"

Repository: wave-av/examples

Length of output: 430


Remove /mcp-server-setup from Dependabot configuration or add a package.json file to that directory.

The configuration for /mcp-server-setup will not work—Dependabot requires a package.json file in each configured directory to manage dependencies. Only /sdk-quickstart and /adk-hello-agent have package.json files.

To fix:

  1. Either remove the /mcp-server-setup entry from .github/dependabot.yml
  2. Or add a package.json file to /mcp-server-setup if it should have npm dependencies managed

Additionally, consider these improvements for the remaining directories:

  • Add open-pull-requests-limit to prevent excessive simultaneous PRs:
- package-ecosystem: npm
  directory: /sdk-quickstart
  schedule:
    interval: weekly
  open-pull-requests-limit: 10
  • Add grouping rules to batch dependency updates by type and reduce PR noise
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/dependabot.yml around lines 3 - 14, The dependabot config contains
an entry for /mcp-server-setup but that directory lacks a package.json so
Dependabot will fail; either remove the /mcp-server-setup stanza from
.github/dependabot.yml or add a valid package.json to /mcp-server-setup so npm
updates can run, and for the remaining entries (e.g., /sdk-quickstart and
/adk-hello-agent) add an open-pull-requests-limit setting
(open-pull-requests-limit: 10) and optional grouping rules to batch updates by
type to reduce PR noise.

@wave-bugbot

wave-bugbot Bot commented Jun 7, 2026

Copy link
Copy Markdown

🟢 WAVE BugBot — clear

No confident findings on the changed lines.

Local review · $0 inference · wave-dispatch

@yakimoto yakimoto closed this Aug 12, 2026
@yakimoto yakimoto reopened this Aug 12, 2026
@cursor

cursor Bot commented Aug 12, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_a26b58a4-fe11-4437-9374-f46ded238330)

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Add Dependabot config for example npm projects

⚙️ Configuration changes ✨ Enhancement 🕐 Less than 5 minutes

Grey Divider

AI Description

• Enable weekly Dependabot updates for npm dependencies in example directories.
• Keep /sdk-quickstart, /mcp-server-setup, and /adk-hello-agent package versions current
 automatically.
Diagram

graph TD
  GH["GitHub Repo"] --> DB["Dependabot"] --> CFG[".github/dependabot.yml"] --> SDK["/sdk-quickstart"]
  CFG --> MCP["/mcp-server-setup"]
  CFG --> ADK["/adk-hello-agent"]

  subgraph Legend
    direction LR
    _sys["System"] ~~~ _cfg["Config"] ~~~ _dir["Directory"]
  end
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Add grouping/labels and PR limits in Dependabot
  • ➕ Reduces PR noise by batching related dependency bumps
  • ➕ Improves triage via labels/assignees/reviewers
  • ➕ Can cap open PRs to avoid backlog
  • ➖ Slightly more configuration to maintain
  • ➖ Grouping rules may mask which subproject needs a specific update
2. Consolidate examples into a workspace/monorepo dependency model
  • ➕ Single set of dependency updates instead of three independent streams
  • ➕ Potentially fewer lockfile conflicts across examples
  • ➖ Higher structural change to repo layout
  • ➖ May not match goal of keeping examples independent and copyable

Recommendation: Current approach (one Dependabot entry per example directory) is the simplest and most explicit. Consider a follow-up to add labels, open-pull-requests-limit, and optional dependency groups if weekly updates generate too many PRs.

Files changed (1) +14 / -0

Other (1) +14 / -0
dependabot.ymlConfigure weekly npm Dependabot updates for three example directories +14/-0

Configure weekly npm Dependabot updates for three example directories

• Adds a Dependabot v2 configuration enabling weekly npm dependency update checks for '/sdk-quickstart', '/mcp-server-setup', and '/adk-hello-agent'. This ensures automated PRs are created to keep example dependencies up to date.

.github/dependabot.yml

Co-authored-by: Codesmith <codesmith-bot@users.noreply.github.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Risk: low. Left a non-blocking comment because Cursor Bugbot and Cursor Security Agent both skipped and did not complete successfully, so this cannot be auto-approved. Human review is needed; no eligible non-author reviewers were available to assign.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router and Approver

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Devin Review found 2 potential issues.

Open in Devin Review

Comment thread .github/dependabot.yml
Comment thread .github/dependabot.yml
Comment on lines +1 to +12
version: 2
updates:
- package-ecosystem: npm
directory: /sdk-quickstart
schedule:
interval: weekly
open-pull-requests-limit: 10
- package-ecosystem: npm
directory: /adk-hello-agent
schedule:
interval: weekly
open-pull-requests-limit: 10

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 No lockfiles present; updates will be manifest-only

The repo contains no package-lock.json/yarn.lock anywhere, so the scheduler will only be able to bump version ranges in the manifests. Since the manifests use caret ranges (e.g. "@wave-av/sdk": "^2.0.0"), most minor/patch releases will not produce any update PR at all — only major bumps will. Worth confirming this matches the intent behind adding the config.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Informational observation, not a config bug: the repo intentionally has no lockfiles, and manifest-only range bumps are the expected Dependabot behavior here. Adding lockfiles is out of scope for this PR.

@qodo-code-review

qodo-code-review Bot commented Aug 12, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📜 Skill insights (0)

Grey Divider


Remediation recommended

1. Invalid Dependabot directory ✓ Resolved 🐞 Bug ≡ Correctness
Description
The new npm update entry targets /mcp-server-setup, but that directory contains no package.json
or other npm manifest. Dependabot therefore cannot discover dependencies there, leaving this update
target ineffective or causing the scheduled update check to fail.
Code

.github/dependabot.yml[R7-10]

+  - package-ecosystem: npm
+    directory: /mcp-server-setup
+    schedule:
+      interval: weekly
Evidence
The configured path is an npm Dependabot target, but the repository tree contains only README.md
under /mcp-server-setup. The other configured paths each contain package.json files, demonstrating
that this entry uniquely lacks the manifest required for npm dependency discovery.

.github/dependabot.yml[7-10]
/mcp-server-setup/README.md[1-1]
/sdk-quickstart/package.json[1-1]
/adk-hello-agent/package.json[1-1]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The Dependabot npm entry for `/mcp-server-setup` points to a directory without an npm manifest, so it cannot produce dependency updates.

## Issue Context
The repository contains `/mcp-server-setup/README.md` only, while `/sdk-quickstart/package.json` and `/adk-hello-agent/package.json` are valid npm manifests.

## Fix Focus Areas
- .github/dependabot.yml[7-10]

Remove the invalid entry, or change its directory to the location of the intended npm manifest if one is added.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Context
✅ Compliance rules (platform): 2 rules
Review mode: 🚀 Fast: This is a small, localized Dependabot configuration addition with three straightforward npm update entries and no security-sensitive application logic or broad behavioral impact.

Grey Divider

Tip of the day
💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

qodo-code-review[bot]

This comment was marked as resolved.

@qodo-code-review

Copy link
Copy Markdown

Qodo Fixer

No findings are within the configured fix scope. To change which findings are fixed, adjust the setting on your Qodo configuration page.

macroscopeapp[bot]
macroscopeapp Bot previously approved these changes Aug 12, 2026
@macroscopeapp

macroscopeapp Bot commented Aug 12, 2026

Copy link
Copy Markdown

Approvability

Verdict: Approved 6ef1b7a

This PR adds standard Dependabot configuration for automated npm dependency updates. The change is CI/CD-only with no runtime behavior impact. The CodeRabbit finding about /mcp-server-setup is factually incorrect - that directory is not in the actual config.

You can customize Macroscope's approvability policy. Learn more.

Co-authored-by: Codesmith <codesmith-bot@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.

1 participant