Closes #3104 

This slightly loosens the engine check to be `>=10.13` which is when Node 10 first went into LTS. 

This reverts commit 514d527d.

Adds a new `rangeStrategy` value `lockfile-update'. Enabling this means you will get PRs that contain updates for the versions in your lock file (currently npm and yarn only) even if the range in the `package.json` file hasn't changed because the update is "in range".

Closes #1382 

forgotten in 8796b612

fixes `Error: Cannot find module '/usr/src/app/bin/yarn-1.10.1.js'`

Automerge branch even if PR has previously been raised, so long as only one commit exists. This handles the case where an initial update e.g. v1.0.1 fails, causing PR to be raised, but then a v1.0.2 is published which fixes the failure.

Closes #1381

Redesigns Renovate’s Dockerfile to use Ubuntu 18 as its base.

Closes #3063

BREAKING CHANGE: Renovate now requires Node.js 10.x to run

Rename all VSTS references to be Azure DevOps.

Closes #2810

BREAKING CHANGE: 'vsts' platform is now renamed to 'azure'

Deprecate use of “special” env var like `GITHUB_TOKEN` and instead standardize on `RENOVATE_*` environment variables instead.

Closes #2834

BREAKING CHANGE: For GitHub, GitLab, Bitbucket and VSTS you need to migrate `*_ENDPOINT` to `RENOVATE_ENDPOINT`, `*_TOKEN` to `RENOVATE_TOKEN`, and same for `BITBUCKET_USERNAME` and `BITBUCKET_PASSWORD`.

I haven’t used Heroku with Renovate in over a year and am not able to directly support it. I think it would be best to be made into a “wrapper” repository like https://github.com/renovatebot/renovate-heroku

BREAKING CHANGE: renovate repository no longer supports direct deployment to Heroku