Skip to content

Configure Renovate

Renovate Bot requested to merge renovate/configure into develop

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

  • Gemfile (bundler)
  • .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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 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 2 Merge Requests:

Update ruby Docker tag to v2.7
  • Schedule: ["at any time"]
  • Branch name: renovate/ruby-2.x
  • Merge into: develop
  • Upgrade ruby to 2.7
Update ruby Docker tag to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/ruby-3.x
  • Merge into: develop
  • Upgrade ruby to 3.4

❓ 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