Configure Renovate

[renovate[bot]]

Welcome to Renovate!

This is an onboarding PR to help you understand and configure Renovate before any regular Pull Requests begin. Once you close this Pull Request, Renovate will begin keeping your dependencies up-to-date via automated Pull Requests.

If you have any questions, try reading our Configuring Renovate help page first, or feel free to ask the app author @rarkins a question in a comment below.

---

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
• Combine any patch and minor upgrades together into same branch/PR
• 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
• Update existing lock files only when package.json is modified
• Autodetect whether to pin dependencies or maintain ranges
• Odd version numbers are classified as unstable
• Preconfigure dependencies where an odd leading digit indicates unstable
• Pin dependency versions for devDependencies and retain semver ranges for others

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.

---

What to Expect

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

1. Update dependency execa to ^0.8.0

   • Branch name: renovate/execa-0.x
   • Upgrades execa in dependencies from ^0.6.0 to ^0.8.0

2. Update dependency faye-websocket to v0.11.1

   • Branch name: renovate/faye-websocket-0.x
   • Upgrades faye-websocket in npmDepends from 0.11.0 to 0.11.1

3. Update dependency lolex to v1.6.0

   • Branch name: renovate/lolex-1.x
   • Upgrades lolex in npmDepends from 1.4.0 to 1.6.0

4. Update dependency lolex to v2

   • Branch name: renovate/lolex-2.x
   • Upgrades lolex in npmDepends from 1.4.0 to 2.3.1

5. Update dependency permessage-deflate to v0.1.6

   • Branch name: renovate/permessage-deflate-0.x
   • Upgrades permessage-deflate in npmDepends from 0.1.3 to 0.1.6

6. Update dependency socket.io to v1.7.4

   • Branch name: renovate/socket.io-1.x
   • Upgrades socket.io in npmDepends from 1.7.3 to 1.7.4

7. Update dependency socket.io to v2

   • Branch name: renovate/socket.io-2.x
   • Upgrades socket.io in npmDepends from 1.7.3 to 2.0.4

8. Update dependency reify to v0.13.0

   • Branch name: renovate/reify-0.x
   • Upgrades reify in npmDepends from 0.6.6 to 0.13.0

---

Don't want a renovate.json file?

Renovate will begin once this "Configure Renovate" PR is merged or closed, but it's recommended that you add the renovate.json to your repository to ensure behaviour matches what you see described here. Alternatively, you can add the same configuration settings into a "renovate" section of your package.json file(s) in this branch and delete the renovate.json from this PR.

Want to start over?

If you'd like Renovate to recreate this "Configure Renovate" PR from scratch - for example if your base branch has had substantial changes - then you need to:

1. (IMPORTANT) Rename this PR to something else, e.g. "Configure Renovate - old"
2. Close the PR and delete the branch

If later on you ever wish to reconfigure Renovate then you can use this same trick of renaming the PR, but you'll also need to delete any renovate.json file too. You should then get a new "Configure Renovate" PR like this.