📝 Description
Currently, we need an automated way to keep our repos' dependencies up to date. While GitHub's Dependabot is great, Renovate offers much stronger capabilities for managing complex monorepos, grouping dependency updates into single PRs (e.g., updating all ESLint plugins at once), and setting up auto-merge rules.
We want to adopt a dual-bot strategy:
- Dependabot: Only used for critical security alerts and vulnerability patching.
- Renovate: Used for all standard, non-security dependency upgrades (npm, github actions, etc.).
✅ Acceptance Criteria (To-do)
🔗 Context
Using both tools gives us the best of both worlds: Dependabot's native integration with GitHub's security advisories, and Renovate's superior flexibility for keeping a monorepo modern without drowning in PRs.
Relevant Documentation:
📝 Description
Currently, we need an automated way to keep our repos' dependencies up to date. While GitHub's Dependabot is great, Renovate offers much stronger capabilities for managing complex monorepos, grouping dependency updates into single PRs (e.g., updating all ESLint plugins at once), and setting up auto-merge rules.
We want to adopt a dual-bot strategy:
✅ Acceptance Criteria (To-do)
renovate.json(or.github/renovate.json) at the root of the repositories.@typescript-eslint/*packages together to reduce PR spam).dependabot.ymlto only alert/patch security vulnerabilities (disable daily/weekly version updates so it doesn't conflict with Renovate).🔗 Context
Using both tools gives us the best of both worlds: Dependabot's native integration with GitHub's security advisories, and Renovate's superior flexibility for keeping a monorepo modern without drowning in PRs.
Relevant Documentation: