Configure Renovate

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)
• requirements.txt (pip_requirements)

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.
• If automerging, push the new commit directly to the base branch (no MR).
• Update lint packages automatically if tests pass.
• Automerge patch upgrades if they pass tests.
• Update testing packages automatically if tests pass.
• Update @types/* packages automatically if tests pass.
• Disable Renovate Dependency Dashboard creation.
• Apply label dependencies to MRs.
• Run lock file maintenance (updates) early Monday mornings.
• Pin dependency versions for devDependencies and retain SemVer ranges for others.
• Wait for branch tests to pass or fail before creating the MR.
• Rebase existing MRs any time the base branch has been updated.
• Use semantic prefixes for commit messages and MR titles.
• Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.

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

chore(deps): update dependency pyyaml to v6.0.1

• Schedule: ["at any time"]
• Branch name: renovate/pyyaml-6.0.x
• Merge into: main
• Upgrade PyYAML to ==6.0.1

chore(deps): update dependency requests to v2.28.2

• Schedule: ["at any time"]
• Branch name: renovate/requests-2.28.x
• Merge into: main
• Upgrade requests to ==2.28.2

chore(deps): update dependency urllib3 to v1.26.16

• Schedule: ["at any time"]
• Branch name: renovate/urllib3-1.26.x
• Merge into: main
• Upgrade urllib3 to ==1.26.16

chore(deps): update dependency requests to v2.31.0

• Schedule: ["at any time"]
• Branch name: renovate/requests-2.x
• Merge into: main
• Upgrade requests to ==2.31.0

chore(deps): update python docker tag to v3.11

• Schedule: ["at any time"]
• Branch name: renovate/python-3.x
• Merge into: main
• Upgrade python to 3.11

chore(deps): update dependency urllib3 to v2

• Schedule: ["at any time"]
• Branch name: renovate/urllib3-2.x
• Merge into: main
• Upgrade urllib3 to ==2.0.3

🚸 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.