Skip to content
GitLab

Configure Renovate

Open 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

  • docker/docker-compose.yml (docker-compose)
  • docker/Dockerfile (dockerfile)
  • .gitlab-ci.yml (gitlabci)
  • pyproject.toml (poetry)
  • .pre-commit-config.yaml (pre-commit)

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 Renovate detects semantic commits, it will use semantic commit type fix for dependencies and chore for all others.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Automatically detect the best rangeStrategy to use.
  • 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.
  • A collection of workarounds for known problems with packages.
  • Append Signed-off-by: to signoff Git commits.
  • Apply label renovate to MRs.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Remove hourly and concurrent rate limits.
  • 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 13 Merge Requests:

chore(deps): update docker docker tag to v19.03.15
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-19.x
  • Merge into: master
  • Upgrade docker to 19.03.15
chore(deps): update registry.cri.epita.fr/cri/docker/mirror/python docker tag to v3.11
  • Schedule: ["at any time"]
  • Branch name: renovate/registry.cri.epita.fr-cri-docker-mirror-python-3.x
  • Merge into: master
  • Upgrade registry.cri.epita.fr/cri/docker/mirror/python to 3.11-slim
chore(deps): update dependency pre-commit to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/pre-commit-3.x
  • Merge into: master
  • Upgrade pre-commit to ^3.0.0
chore(deps): update docker docker tag to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-24.x
  • Merge into: master
  • Upgrade docker to 24.0.7
fix(deps): update dependency attrs to v23
  • Schedule: ["at any time"]
  • Branch name: renovate/attrs-23.x
  • Merge into: master
  • Upgrade attrs to ^23.0.0
fix(deps): update dependency django to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/django-4.x
  • Merge into: master
  • Upgrade Django to ^4.2
fix(deps): update dependency django-debug-toolbar to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/django-debug-toolbar-4.x
  • Merge into: master
  • Upgrade django-debug-toolbar to ^4.2
fix(deps): update dependency gunicorn to v21
  • Schedule: ["at any time"]
  • Branch name: renovate/gunicorn-21.x
  • Merge into: master
  • Upgrade gunicorn to ^21.0.0
fix(deps): update dependency ipython to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/ipython-8.x
  • Merge into: master
  • Upgrade ipython to ^8.0.0
fix(deps): update dependency social-auth-app-django to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/social-auth-app-django-5.x
  • Merge into: master
  • Upgrade social-auth-app-django to ^5.0.0
fix(deps): update dependency social-auth-backend-epita to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/social-auth-backend-epita-2.x
  • Merge into: master
  • Upgrade social-auth-backend-epita to ^2.0.0
fix(deps): update dependency social-auth-core to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/social-auth-core-4.x
  • Merge into: master
  • Upgrade social-auth-core to ^4.0.0
chore(deps): 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 Renovate Bot

Merge request reports