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 Getting Started Configuring Renovate page first.

---

Configuration Summary

Based on the currently configured presets, Renovate will:

• Start dependency updates once this Configure Renovate PR is merged or closed
• Pin dependency versions for devDependencies and retain semver ranges for others
• Separate major versions of dependencies into individual branches/PRs
• Use the same branch/PR for both patch and minor upgrades of a dependency
• Only upgrade to stable npm versions
• Upgrade versions up to the "latest" tag in npm registry
• Create branches/PRs for dependency upgrades as soon as they're available
• Wait until branch tests have passed or failed before creating the PR
• Use renovate/ as prefix for all branch names
• If semantic commits detected, use fix(deps): for dependencies and chore(deps): for all others
• Disable automerging feature - wait for humans to merge all PRs
• Update existing lock files only when package.json is modified

---

Warnings (7)

Please correct - or verify that you can safely ignore - these warnings before you merge this PR.

• coveralls: Dependency uses tag "latest" as its version so that will never be changed by Renovate
• git-dirty: Dependency uses tag "latest" as its version so that will never be changed by Renovate
• mocha: Dependency uses tag "latest" as its version so that will never be changed by Renovate
• nyc: Dependency uses tag "latest" as its version so that will never be changed by Renovate
• should: Dependency uses tag "latest" as its version so that will never be changed by Renovate
• standard: Dependency uses tag "latest" as its version so that will never be changed by Renovate
• standard-markdown: Dependency uses tag "latest" as its version so that will never be changed by Renovate

---

It looks like your repository dependencies are already up-to-date and no initial Pull Requests will be necessary.

Sometimes you may see multiple options for the same dependency (e.g. pinning in one branch and upgrading in another). This is expected and allows you the flexibility to choose which to merge first. Once you merge any PR, others will be updated or removed the next time Renovate runs.

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.

Our Configuration Docs should be helpful if you wish to modify any behaviour.

---

Don't want a renovate.json file?

You are not required to merge this Pull Request - Renovate will begin even if this "Configure Renovate" PR is closed unmerged and without a renovate.json file. However, it's recommended that you add configuration 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. If you make these configuration changes in this branch then the results will be described in this PR after the next time Renovate runs.

[coveralls]

Coverage remained the same at 100.0% when pulling 92a2680c547ee394bd61687b3eab99f250960347 on renovate/configure into cef5a8cd0988dc6b401a9896fcf8b22ac6b7b80e on master.