Home of the Renovate CLI: Cross-platform Dependency Automation by Mend.io
Find a file
Rhys Arkins cbdad22a7d
docs: Improve local development information (#1600)
docs: Improve local development information
2018-03-06 10:50:39 +01:00
bin docs: remove docs/configuration options 2018-01-11 10:49:21 +01:00
docs docs: Improve local development information (#1600) 2018-03-06 10:50:39 +01:00
lib fix(allow-failure): enabled automerge when allowed failures occur 2018-03-05 21:18:51 +01:00
test fix(allow-failure): enabled automerge when allowed failures occur 2018-03-05 21:18:51 +01:00
website/docs/_posts docs: fix packageFiles description 2018-03-05 06:34:34 +01:00
.editorconfig Add editorconfig 2017-01-15 17:23:34 +01:00
.eslintignore chore: fix eslint (#793) 2017-09-13 21:43:52 +02:00
.eslintrc.js chore: implement require-await eslint rule (#1095) 2017-11-03 11:56:25 +01:00
.gitattributes Add .gitattributes 2017-01-15 17:25:51 +01:00
.gitignore feat: expose env to npmrc and npm/yarn/pnpm (#1407) 2018-01-25 10:38:30 +01:00
.prettierignore refactor: use prettier instead of eslint-plugin-prettier (#864) 2017-10-01 07:06:06 +02:00
.travis.yml chore: run travis builds only on master 2018-01-26 10:38:28 +01:00
contributing.md docs: Improve local development information (#1600) 2018-03-06 10:50:39 +01:00
license Add license file 2017-01-15 17:27:41 +01:00
package.json fix: update dependency js-yaml to v3.11.0 2018-03-05 16:28:51 +00:00
Procfile fix: Heroku Procfile should use start and not start-raw 2017-11-01 15:28:07 +01:00
readme.md docs: add contributing link inside main readme 2018-03-05 09:08:20 +01:00
yarn.lock fix: update dependency js-yaml to v3.11.0 2018-03-05 16:28:51 +00:00

Renovate banner

Renovate

Automated dependency updates. Flexible, so you don't need to be.

GitHub license codecov Join the chat at https://gitter.im/renovate-app/Lobby Renovate enabled

Why Use Renovate?

  • Receive automated Pull Requests whenever dependencies need updating. Or whenever you schedule it for.
  • Renovate discovers and processes all dependency files in a repository (e.g. supports monorepo architecture such as lerna or yarn workspaces)
  • Extremely customisable behaviour via configuration files or within your package.json
  • Use eslint-like shared config presets for ease of use and simplifying configuration
  • Update lock files natively in the same commit, including immediately resolving conflicts whenever PRs are merged
  • Supports GitHub, GitLab (APIv4) and VSTS. BitBucket is a WIP.
  • Open source (installable via npm/yarn) so can be self-hosted or used for free via GitHub App

Who Uses Renovate?

Renovate was released in 2017 and is now widely used in the developer community. Example users include the following GitHub organisations:

algolia angular mozilla uber-workflow yarnpkg






The Renovate Approach

  • Everyone can benefit from automation, whether it's a little or a lot
  • Renovate should not cause you to change your workflow against your wishes - don't enforce opinions on users
  • All behaviour should be configurable, down to a ridiculous level if desired
  • Autodetect settings wherever possible (to minimise configuration) but always allow overrides

Using Renovate

The easiest way to use Renovate if you are on GitHub is to use the Renovate app. Go to https://github.com/apps/renovate to install it now.

Configuration

The Configuration and Configuration FAQ documents should be helpful.

You can also raise an issue in https://github.com/renovateapp/config-help if you'd like to get your config reviewed or ask any questions.

Self-Hosting

If you are not on GitHub or you prefer to run your own copy of Renovate, then it takes only seconds to set up. Please see docs/self-hosting.md for instructions.

Contributing

If you would like to contribute to Renovate or get a local copy running for some other reason, please see the instructions in contributing.md.

Security / Disclosure

If you discover any important bug with Renovate that may pose a security problem, please disclose it confidentially to security@renovateapp.com 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.