# 📖 Dependabot configuration — automated dependency updates for npm and GitHub Actions # Checks weekly for new versions and opens PRs with changelogs # # 🆕 Groups: batches related updates into a single PR instead of 1 PR per dep. # • npm patch+minor → 1 PR (safe, reviewable in bulk) # • npm major → 1 PR (breaking changes deserve focused review) # • github-actions → 1 PR (actions are typically backwards-compatible) # Result: typically 3 PRs/week instead of 7+ individual ones. version: 2 updates: # npm dependencies - package-ecosystem: npm directory: / schedule: interval: weekly day: monday # 📖 Wait 7 days before proposing freshly published versions: brand-new releases # 📖 can be yanked or malicious, a cooldown gives the ecosystem time to react. cooldown: default-days: 7 open-pull-requests-limit: 5 commit-message: prefix: deps include: scope labels: - dependencies # 📖 chalk 6 requires Node >= 22 but the package supports Node >= 18 (engines field). # 📖 Ignore its major until the minimum Node version is raised to 22. ignore: - dependency-name: "chalk" update-types: ["version-update:semver-major"] groups: # 🟢 Batch all minor + patch updates together — usually safe patch-and-minor: patterns: - "*" update-types: - "minor" - "patch" # 🟡 Batch all major updates together — needs human review for breaking changes major-updates: patterns: - "*" update-types: - "major" # GitHub Actions versions - package-ecosystem: github-actions directory: / schedule: interval: weekly day: monday # 📖 Same 7-day cooldown as npm: newly published action tags can be unstable. cooldown: default-days: 7 open-pull-requests-limit: 3 commit-message: prefix: ci include: scope labels: - dependencies - github-actions groups: # 🟢 Batch all GitHub Actions updates — actions are typically backwards-compatible github-actions: patterns: - "*"