This is an onboarding PR to help you understand and configure Renovate before regular Pull Requests begin. Once you merge or close this Pull Request, Renovate will begin keeping your dependencies up-to-date.
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.
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
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
Preconfigure dependencies where an odd major version indicates unstable (Docker-only)
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 3 Pull Requests:
Coverage remained the same at 100.0% when pulling db2c06c7ce345c039f03bbe1c45f7ed8d62b28aa on renovate/configure into a30ec3d21640d2b880e716effc7cd20b02b44e48 on master.
Welcome to Renovate!
This is an onboarding PR to help you understand and configure Renovate before regular Pull Requests begin. Once you merge or close this Pull Request, Renovate will begin keeping your dependencies up-to-date.
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.
Configuration Summary
Based on the currently configured presets, Renovate will:
renovate/
as prefix for all branch namesfix
for dependencies andchore
for all othersnode_modules
,bower_components
, and various test/tests directoriespackage.json
is modifiedWould 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 (theextends
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 3 Pull Requests:
chore(deps): pin dependencies
renovate/pin-dependencies
devDependencies
to2.6.2
devDependencies
to1.6.0
devDependencies
to5.9.1
devDependencies
to22.0.1
devDependencies
to1.10.2
devDependencies
to9.1.6
devDependencies
to21.2.1
devDependencies
to3.0.0
devDependencies
to5.0.1
devDependencies
to1.6.7
devDependencies
to8.5.8
dependencies
to4.16.2
chore(deps): update dependency @types/node to v9
renovate/node-9.x
devDependencies
from^8.0.57
to9.3.0
chore(deps): update dependency jest to v22
renovate/jest-monorepo
devDependencies
from^21.2.1
to22.0.5