Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

Renovate will begin keeping your dependencies up-to-date only once you merge this Pull Request.
If you close this Pull Request unmerged, then Renovate will be disabled.

If you have any questions, try reading our Docs, particularly the Getting Started section.
You can post questions in our Config Help repository or @ the app author @rarkins in this PR and he'll probably see it.

---

Detected Package Files

• package.json (npm)

Configuration Summary

Based on the currently configured presets, Renovate will:

• Start dependency updates once this Configure Renovate PR is merged or closed
• Separate major versions of dependencies into individual branches/PRs
• Do not separate patch and minor upgrades into separate PRs for the same dependency
• Upgrade to unstable versions only if the existing version is unstable
• Raise PRs immediately (after branch is created)
• Use renovate/ as prefix for all branch names
• If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
• Keep existing branches updated even when not scheduled
• Disable automerging feature - wait for humans to merge all PRs
• Ignore node_modules, bower_components, and various test/tests directories
• Update existing lock files only when package.json is modified
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 20 concurrent Renovate PRs at any time
• Run lock file maintenance (updates) early Monday mornings
• Wait until branch tests have passed or failed before creating the PR
• Disable semantic prefixes for commit messages and PR titles
• Set a status check to warn when upgrades < 24 hours old might get unpublished

Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch and this Pull Request description will be updated the next time Renovate runs. Try to use Config Presets (the extends array) when possible rather than raw config, as then this PR will be able to more accurately describe your settings.

---

What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

1. Update dependency deepmerge to v2

• Branch name: renovate/deepmerge-2.x
• Upgrades deepmerge in dependencies from ^1.5.2 to ^2.0.0

2. Lock file maintenance

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/lock-file-maintenance
• Regenerates lock file to use latest dependency versions

---

---

This PR has been generated by Renovate Bot.

[edmorley]

I've enabled Renovate so (a) we get lockfile updates (current lockfile has a upath version that errors with node 10), and (b) since we're about to gain more dependencies that we should keep up to date (#53).