Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.
To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.
Detected Package Files
docker-compose-tools.yml (docker-compose)
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 fix for dependencies and chore for all others if semantic commits are in use.
Ignore node_modules, bower_components, vendor and 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.
Do you want to change how Renovate upgrades your dependencies? Add your custom config to 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 6 Merge Requests:
Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.
Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.
