Universal dependency update tool that fits into your workflows.
 
 
 
 
 
 
Go to file
Rhys Arkins 1f28f54cc0 8.1.0 2017-01-31 12:37:51 +01:00
bin Fix update-docs path 2017-01-31 12:36:22 +01:00
docs Update docs 2017-01-30 07:37:43 +01:00
lib Use async await (#78) 2017-01-31 12:19:06 +01:00
test Use async await (#78) 2017-01-31 12:19:06 +01:00
.editorconfig Add editorconfig 2017-01-15 17:23:34 +01:00
.eslintrc.js Use async await (#78) 2017-01-31 12:19:06 +01:00
.gitattributes Add .gitattributes 2017-01-15 17:25:51 +01:00
.gitignore Use async await (#78) 2017-01-31 12:19:06 +01:00
.npmignore Ignore bin 2017-01-20 14:09:57 +01:00
Procfile Add web server for Heroku 2017-01-16 10:35:03 +01:00
circle.yml Use async await (#78) 2017-01-31 12:19:06 +01:00
license Add license file 2017-01-15 17:27:41 +01:00
package.json 8.1.0 2017-01-31 12:37:51 +01:00
readme.md Update docs 2017-01-30 07:37:43 +01:00

readme.md

renovate

Keep npm dependencies up-to-date

Why

  • Creates or updates Pull Requests for each dependency that needs updating
  • Discovers and processes all package.json files in repository (supports monorepo architecture)
  • Supports multiple major versions per-dependency at once
  • Configurable via file, environment, CLI, and package.json
  • Self-hosted

Install

$ npm install -g renovate

Authentication

You need to select a GitHub user for renovate to assume the identity of. It's recommended that you use a dedicated "bot" account for this to avoid user confusion.

The script will need a GitHub Personal Access Token with "repo" permissions. You can find instructions for generating it here: https://help.github.com/articles/creating-an-access-token-for-command-line-use/

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 GITHUB_TOKEN.

Usage

$ node renovate --help

  Usage: renovate [options] [repositories...]

  Options:

    -h, --help                   output usage information
    --enabled [boolean]          Enable or disable renovate
    --onboarding [boolean]       Require a Configuration PR first
    --token <string>             GitHub Auth Token
    --package-files <list>       Package file paths
    --dep-types <list>           Dependency types
    --ignore-deps <list>         Dependencies to ignore
    --ignore-future [boolean]    Ignore versions tagged as "future"
    --ignore-unstable [boolean]  Ignore versions with unstable semver
    --respect-latest [boolean]   Ignore versions newer than npm "latest" version
    --recreate-closed [boolean]  Recreate PRs even if same ones were closed previously
    --labels <list>              Labels to add to Pull Request
    --assignees <list>           Assignees for Pull Request
    --log-level <string>         Logging level

  Examples:

    $ renovate --token abc123 singapore/lint-condo
    $ renovate --ignore-unstable=false --log-level verbose singapore/lint-condo
    $ renovate singapore/lint-condo singapore/package-test

Note: The first time you run renovate on a repository, it will not upgrade any dependencies. Instead, it will create a PR 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 first disable the onboarding setting before running.

Deployment

See deployment docs for details.

Design Decisions

See design decisions doc for details.