Skip to content
GitLab

Configure Renovate

Merged CRI Renovate Bot requested to merge renovate/configure into master

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

  • .gitlab-ci.yml (gitlabci)
  • pyproject.toml (poetry)

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 and chore 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 10 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 web3j 5.0.0 release
  • 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
  • Do not upgrade from Alpine stable to edge
  • Append Git Signed-off-by: signature to Git commits.
  • Apply label renovate to MRs
  • Preserve (but continue to upgrade) any existing SemVer ranges
  • Remove hourly and concurrent rate limits
  • Rebase existing MRs any time the base branch has been updated
  • Enable Renovate Dependency Dashboard creation
  • Raise MR when vulnerability alerts are detected
  • Enable the pre-commit manager
  • Default preset for use with the CRI's repos

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the 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 dependency squidfunk/mkdocs-material to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/squidfunk-mkdocs-material-8.x
  • Merge into: master
  • Upgrade squidfunk/mkdocs-material to 8.2.4
Lock file maintenance
  • Schedule: ["before 5am on monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: master
  • Regenerate lock files to use latest dependency versions

❓ 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.

This MR has been generated by Renovate Bot.

Edited by CRI Renovate Bot