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.
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
With your current configuration, renovate will initially create the following Pull Requests:
Pull Requests (7)
Update dependency firebase-admin to ^5.0.0
Branch name: renovate/firebase-admin-5.x
Upgrades firebase-admin in dependencies from ^4.0.3 to ^5.0.0
Update dependency codecov to v2
Branch name: renovate/codecov-2.x
Upgrades codecov in devDependencies from ^1.0.1 to 2.3.0
Pin Dependencies
Branch name: renovate/pin-dependencies
Pins jest in devDependencies from ^17.0.3 to 17.0.3
Pins eslint in devDependencies from ^3.11.0 to 3.19.0
Pins codecov in devDependencies from ^1.0.1 to 1.0.1
Update dependency eslint to v4
Branch name: renovate/eslint-4.x
Upgrades eslint in devDependencies from ^3.11.0 to 4.5.0
Update dependency jest to v18
Branch name: renovate/jest-18.x
Upgrades jest in devDependencies from ^17.0.3 to 18.1.0
Update dependency jest to v19
Branch name: renovate/jest-19.x
Upgrades jest in devDependencies from ^17.0.3 to 19.0.2
Update dependency jest to v20
Branch name: renovate/jest-20.x
Upgrades jest in devDependencies from ^17.0.3 to 20.0.4
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.
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:
devDependenciesand retain semver ranges for othersrenovate/as prefix for all branch namesfix(deps):for dependencies andchore(deps):for all otherspackage.jsonis modifiedWith your current configuration, renovate will initially create the following Pull Requests:
renovate/firebase-admin-5.xdependenciesfrom^4.0.3to^5.0.0renovate/codecov-2.xdevDependenciesfrom^1.0.1to2.3.0renovate/pin-dependenciesdevDependenciesfrom^17.0.3to17.0.3devDependenciesfrom^3.11.0to3.19.0devDependenciesfrom^1.0.1to1.0.1renovate/eslint-4.xdevDependenciesfrom^3.11.0to4.5.0renovate/jest-18.xdevDependenciesfrom^17.0.3to18.1.0renovate/jest-19.xdevDependenciesfrom^17.0.3to19.0.2renovate/jest-20.xdevDependenciesfrom^17.0.3to20.0.4Sometimes 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.jsonin 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.jsonfile?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.jsonfile. 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.jsonfile(s) in this branch and delete therenovate.jsonfrom 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.