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
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.
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.
Pin Docker digests.
Pin github-action digests.
Enable Renovate configuration migration MRs when needed.
Pin dependency versions for development dependencies.
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 1 Merge Request:
Pin dependencies
Schedule: ["at any time"]
Branch name: renovate/pin-dependencies
Merge into: main
Upgrade gcr.io/kaniko-project/executor to sha256:2562c4fe551399514277ffff7dcca9a3b1628c4ea38cb017d7286dc6ea52f4cd
Upgrade postgres to sha256:aef2e621d89d3a2e6bd1fb1bc8b066277425ea60fa1d97e87ee8894c9efc0272
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.
Tine Wittler authored