chore: Configure Renovate

renovaterequested to merge
renovate/configure into main

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 (pep621)

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.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration MRs when needed.
  • Pin dependency versions for development dependencies.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.

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

chore(deps): update dependency to-be-continuous/python to v7.15.0
  • Schedule: ["at any time"]
  • Branch name: renovate/to-be-continuous-python-7.x
  • Merge into: main
  • Upgrade to-be-continuous/python to 7.15.0
chore(deps): update dependency to-be-continuous/python to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/to-be-continuous-python-9.x
  • Merge into: main
  • Upgrade to-be-continuous/python to 9.1.0

❓ 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