Skip to content

Configure Renovate

RenovateBot 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-compose.yml (docker-compose)
  • .gitlab-ci.yml (gitlabci)
  • package.json (npm)

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
  • 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

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

Update dependency husky to v5.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/devdependencies-(non-major)
  • Merge into: master
  • Upgrade husky to 5.2.0
Update Node.js to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/node-17.x
  • Merge into: master
  • Upgrade node to 17
Update dependency bootstrap to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/bootstrap-5.x
  • Merge into: master
  • Upgrade bootstrap to ^5.0.0
Update dependency concurrently to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/concurrently-7.x
  • Merge into: master
  • Upgrade concurrently to ^7.0.0
Update dependency husky to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-7.x
  • Merge into: master
  • Upgrade husky to 7.0.4
Update dependency ionicons to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/ionicons-6.x
  • Merge into: master
  • Upgrade ionicons to ^6.0.0
Update dependency node-sass to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/node-sass-7.x
  • Merge into: master
  • Upgrade node-sass to ^7.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam 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.

This MR has been generated by Renovate Bot.

Merge request reports