Keep dependencies up-to-date.
package.jsonfiles in repository (supports monorepo architecture including yarn workspaces)
If you would like help on your Renovate configuration, or simply get someone to review it, we have created a config-help repository https://github.com/renovateapp/config-help/issues where you can post an issue with your config.
Renovate is now available as a free GitHub "App". Go to https://github.com/apps/renovate to enable it now.
$ npm install -g renovate
You need to select a repository user for
renovate to assume the identity of,
and generate a Personal Access Token. It's strongly recommended that you use a
dedicated "bot" account for this to avoid user confusion and to avoid the
Renovate bot mistaking changes you have made or PRs you have raised for its own.
You can find instructions for GitHub here (select "repo" permissions)
You can find instructions for GitLab here. Note: GitLab APIv3 is no longer supported - please upgrade to GitLab APIv4 before testing Renovate.
You can find instructions for VSTS vsts.
This token needs to be configured via file, environment variable, or CLI. See
docs/configuration.md for details. The simplest way is
to expose it as
renovate --help for usage details.
Note: The first time you run
renovate on a repository, it will not upgrade any
dependencies. Instead, it will create a Pull Request (Merge Request if GitLab)
called 'Configure Renovate' and commit a default
renovate.json file to the
repository. This PR can be close unmerged if the default settings are fine for
you. Also, this behaviour can be disabled if you set the
configuration option to
false before running.
See deployment docs for details.
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.
See design decisions doc for details.