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
-
docker-compose.yml(docker-compose) -
Dockerfile(dockerfile) -
requirements.txt(pip_requirements) -
renovate.json(renovate-config-presets)
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.
- Use semantic commit type
fixfor dependencies andchorefor all others if semantic commits are in use. - Ignore
node_modules,bower_components,vendorand various test/tests (except for nuget) directories. - Group known monorepo packages together.
- Use curated list of recommended non-monorepo package groupings.
- Show only the Age and Confidence Merge Confidence badges for pull requests.
- Apply crowd-sourced package replacement rules.
- Apply crowd-sourced workarounds for known problems with packages.
- Preserve (but continue to upgrade) any existing SemVer ranges.
- Enable Renovate Dependency Dashboard creation.
- Rebase existing MRs any time the base branch has been updated.
- Raise MR when vulnerability alerts are detected with label
'security'. - Use curated list of recommended non-monorepo package groupings.
renovate.json in this branch. Renovate will update the Merge Request description the next time it runs.
What to Expect
With your current configuration, Renovate will create 3 Merge Requests:
Update dependency minio to v5.0.10
- Schedule: ["at any time"]
- Branch name:
renovate/minio-5.x - Merge into:
master - Upgrade minio to
==5.0.10
Update python Docker tag to v3.13
- Schedule: ["at any time"]
- Branch name:
renovate/python-3.x - Merge into:
master - Upgrade python to
3.13-slim
Update dependency minio to v7
- Schedule: ["at any time"]
- Branch name:
renovate/minio-7.x - Merge into:
master - Upgrade minio to
==7.2.16
prhourlylimit for details.
This MR has been generated by Renovate Bot.