Merge renovate pull requests

When to use:

When doing routinely maintenance and when Renovatebot has created pull requests which are not automatically merged. They pull requests may not have been automatically merged because there's a major version update, the checks failed or other reasons.

Caveats:

• Do not attempt to process pull requests which are not created by Renovatebot (username might be renovate and author id might be app/renovate).
• We should only process open pull requests.
• When updating versions with breaking changes (updating major versions or if the major version is 0) then it's very important to read and understand all the breaking changes and how to update correctly/safely. The breaking changes, and sometimes links to official documentation, can be found in the pull request description or in the changelog of the GitHub repo of the dependency to update. We should follow the official migration guides if available. If the changes are significant, affect the architecture and/or requires migrations on external systems like databases or production systems then we should leave it to the user to resolve it manually. Leave a comment in the pull request explaining this and then abort the current workflow.

Tools:

You may use the GitHub CLI to get fetch pull requests from the GitHub repo, see results from checks etc.

Merge exceptions:

• eslint / eslint monorepo should not be updated to >= v10 yet because they haven't patched a bug.