Configure Renovate
Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.
Detected Package Files
-
Dockerfile
(dockerfile) -
kubernetes/hello-world/busybox-hello-world/Dockerfile.js
(dockerfile) -
kubernetes/hello-world/nginx-hello-world/Dockerfile
(dockerfile) -
.gitlab-ci.yml
(gitlabci)
Configuration Summary
Based on the default config's presets, Renovate will:
- Start dependency updates only once this onboarding MR is merged
- Enable Renovate Dependency Dashboard creation
- If semantic commits detected, use semantic commit type
fix
for dependencies andchore
for all others - Ignore
node_modules
,bower_components
,vendor
and various test/tests directories - Autodetect whether to pin dependencies or maintain ranges
- Rate limit MR creation to a maximum of two per hour
- Limit to maximum 20 open MRs at any time
- Group known monorepo packages together
- Use curated list of recommended non-monorepo package groupings
- Fix some problems with very old Maven commons versions
- Ignore spring cloud 1.x releases
- Ignore http4s digest-based 1.x milestones
- Use node versioning for @types/node
- Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
renovate.json
in this branch with your custom config and the list of Merge Requests in the "What to Expect" section below will be updated the next time Renovate runs.
What to Expect
With your current configuration, Renovate will create 2 Merge Requests:
Update Node.js to v6.17.1
- Schedule: ["at any time"]
- Branch name:
renovate/node-6.x
- Merge into:
master
- Upgrade node to
6.17.1
Update Node.js to v17
- Schedule: ["at any time"]
- Branch name:
renovate/node-17.x
- Merge into:
master
- Upgrade node to
17.1.0
This MR has been generated by Renovate Bot.