Skip to content

ci: configure Renovate

Automation 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)
  • package.json (npm)
  • .nvmrc (nvm)

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 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.
  • Pin Docker digests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Use semantic prefixes for commit messages and MR titles.
  • 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'.
  • Group all minor and patch updates together.
  • Group known monorepo packages together.
  • 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:

chore(deps): pin dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: master
  • Upgrade node to sha256:ad8435d974838c10fdbbbcf607b829cc64131210150ce9585b8292130e677ab4
  • Upgrade sonarsource/sonar-scanner-cli to sha256:43c86163dd6a12a1a68c05c00a9b03948ee28ca45ae2e3fc13c8186acd2c8257
chore(deps): update dependency @testing-library/jest-dom to ~5.17.0
chore(deps): update eslint
fix(deps): update all non-major dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/all-minor-patch
  • Merge into: master
  • Upgrade generate-react-cli to ~5.2.0
  • Upgrade loglevel to ~1.8.0
  • Upgrade node to 16.20.1
  • Upgrade node to sha256:3b9214c4d0540be68e61311afd8819c15c8cd74a0b964a0a8a48eeb41bea57b0
  • Upgrade reactstrap to ~9.2.0
  • Upgrade release-it to ~15.11.0
fix(deps): update dependency react-router-dom to ~6.14.0
  • Schedule: ["at any time"]
  • Branch name: renovate/react-router
  • Merge into: master
  • Upgrade react-router-dom to ~6.14.0
chore(deps): update all major dependencies (major)
chore(deps): update definitelytyped (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-definitelytyped
  • Merge into: master
  • Upgrade @types/jest to ^29.0.0
  • Upgrade @types/node to ^18.0.0

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