ci: add Dependabot with auto-merge for patch/minor updates#34
Conversation
- Daily npm dependency scanning at 6am UK time - Weekly GitHub Actions updates on Mondays - Auto-merge patch and minor updates after CI passes - Major updates require manual review with checklist comment - Groups minor/patch updates to reduce PR noise 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
PR Review: Dependabot with Auto-Merge ConfigurationThanks for setting up automated dependency management. This is a solid approach for keeping the project secure and up-to-date. Here's my feedback: ✅ What Looks Good
🔍 Suggestions for Improvement1. Wait for CI before auto-mergingThe current workflow triggers on # Option: Add a needs dependency on a CI check job
# Or ensure branch protection requires CI to pass before mergeThe current setup should work if branch protection rules require CI to pass, but it's worth verifying that's configured. 2. Consider adding security-versions-only for certain packagesFor security-sensitive dependencies, you might want to only auto-merge security updates: ignore:
- dependency-name: "*"
update-types: ["version-update:semver-major"]3. Branch name mismatchThe PR is from branch 4. Consider adding ecosystem-specific ignoresIf there are packages you never want auto-updated (e.g., packages with known breaking changes in minors), you can add: ignore:
- dependency-name: "some-problematic-package"🔐 Security Considerations
📋 Minor Nits
VerdictApprove with minor suggestions. The implementation follows best practices and should work well with the existing CI setup. The suggestions above are optional enhancements rather than blockers. 🤖 Reviewed by Claude Code |
🤖 Generated with Claude Code