renovate/renovate repository overview

⁠Renovate

Automated dependency updates. Multi-platform and multi-language.

⁠Why Use Renovate?

• Receive automated Pull Requests whenever dependencies need updating
• Define schedules to avoid unnecessary noise in projects (e.g. for weekends or outside of working hours, or weekly updates, etc.)
• Relevant package files are discovered automatically (e.g. supports monorepo architecture such as Lerna or Yarn workspaces without further configuration)
• Bot behavior is extremely customizable via configuration files (config as code)
• Use ESLint-like shared config presets for ease of use and simplifying configuration (JSON format only)
• Lock files are natively supported and updated in the same commit, including immediately resolving conflicts whenever PRs are merged
• Supports GitHub (.com and Enterprise), GitLab (.com and CE/EE), Bitbucket Cloud, Bitbucket Server, Azure DevOps and Gitea.
• Open source (installable via npm/Yarn or Docker Hub) so can be self-hosted or used via GitHub App

⁠Who Uses Renovate?

Renovate was released in 2017 and already is widely used in the developer community, including:

⁠The Renovate Approach

• We believe everyone benefits from automation, whether it's a little or a lot
• Renovate should not cause you to change your workflow against your wishes, instead it should be adaptable to your existing workflow
• All behavior should be configurable, down to a ridiculous level if necessary
• Autodetect settings wherever possible (to minimize configuration) but always allow overrides

⁠Configuration

Visit https://docs.renovatebot.com/⁠ for documentation, and in particular https://docs.renovatebot.com/configuration-options/⁠ for a list of configuration options.

To get help and/or a review for your config, go to the discussions tab in the Renovate repository⁠ and open a new "config help" discussion post.

⁠Security / Disclosure

If you discover any important bug with Renovate that may pose a security problem, please disclose it confidentially to [email protected]⁠ first, so that it can be assessed and hopefully fixed prior to being exploited. Please do not raise GitHub issues for security-related doubts or problems.