renovateRepository now returns “res” - the result of the current renovation, and “status” - the overall status of the repository.

Closes #1786

This hopefully gives a better chance of GitHub being able to finish computing the new mergeability status, and reduces the chance of a race condition.

Closes #1617

This reverts commit dd26a018.

feat: validate renovate config PRs

Refactors all instances of .concat() to use array spread operators instead

Closes #1459

Re-enables branch cleanup for multiple baseBranches

Refactors all non-npm code to live inside lib/manager/*

This reverts commit c4cdfe89.

Adds a config option to bot administrators called `exposeEnv`, for cases where repositories are trusted. If set to true, the bot's full `process.env` can be used for `.npmrc` variable substitution and is passed to child processes when generating lock files. Disabled by default, including in the App.

This PR adds the capability to renovate more than one base branch at a time. For instance, a project may have their released `3.x` version on `master`, while an upcoming `4.x` is being prepared using branch `next`. `4.x` might have a quite different set of dependencies (e.g. some removed or some added) so it's not appropriate to only target `master` and keep rebasing, as it will get messy. Instead, it's necessary to target both `master` and `next` to keep both updated.

Closes #1279

This reverts commit eb579ff3.

For some reason it seems to be causing a reduction in throughput per hour in the app once deployed.

When 404 or 422 errors are encountered writing updates, Renovate will now restart in an attempt to fix it. Usually this is because branches/PRs have been edited or closed while Renovate is running.

Closes #1299

Repository logic code has been rearranged for better logic and file separation.

Closes #654 

This PR refactors the onboarding PR logic into its own subdirectory and redesigns it to use plain markdown instead of html. Plain markdown in PR bodies is a requirement for adding VSTS Support ( #1049 ).

* refactor: move monorepos logic to npm manager

* fix test

Also clarify docs that encrypted config must be contained in renovate.json (i.e. not package.json).

99% of the time we should not Renovate forked repositories. Previously, we skipped onboarding them unless a renovate.json was present. However, that meant that if someone forked a repository where the source was using Renovate, then the fork gets renovated automatically too. After this change, forked repositories need to set renovateFork=true in their renovate.json

Closes #940

BREAKING CHANGE: Forked repositories now need to configure renovateFork=true in renovate.json

* refactor platform

* refactor detect package files

* fix

* refactor npm detect

* refactor meteor detect

* refactor: move detect package files completely to manager

* update snapshots