Previously, Renovate would attempt to keep a branch up to date even if users had edited it. e.g. adding commits on top of the existing branch if newer versions were released. Now, Renovate adds a warning comment if a user has edited a branch, making it clear that responsibility for the branch is over to them and how they can undo this.

Closes #653

Deduplicate changelogs in monorepo PRs. i.e. the same monorepo won’t be included more than once.

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

Closes #1246

This PR adds new checks that:
- Website configuration options are listed in alphabetical order
- Every relevant configuration option in source code is documented on the website
Website docs have been updated accordingly to pass.

Closes #543, Closes #1310

This PR adds the configuration option “commitMessageBody”. The contents of this will be appended to the commitMessage, separated by two line returns.

Detect if the upgraded dependency was already in “resolutions” and update it too if it was an exact match. Warn if it was not.

Closes #1318

Closes #1334

Closes #1311

Now, if every upgrade in a group has the same new version, then the PR title will include this version.

Closes #1332

chore: update dependency nock to v9.1.5

fix: update dependency showdown to v1.8.6

fix: update dependency moment to v2.20.1

(Using Forking Renoate for now)

This PR ports across GitHub’s caching approach to the GitLab platform API.

Renovate will now detect if renovate config already exists within the project’s ‘package.json’ root, and skip onboarding if so.

Closes #1159

Closes #1314