Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• docker/Dockerfile (dockerfile)
• .github/workflows/build.yml (github-actions)
• .github/workflows/greetings.yml (github-actions)
• .github/workflows/release-drafter.yml (github-actions)
• pyproject.toml (pep621)
• requirements.txt (pip_requirements)
• pyproject.toml (poetry)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• 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.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 34 Pull Requests:

Update dependency black to v24 [SECURITY]

• Branch name: renovate/pypi-black-vulnerability
• Merge into: main
• Upgrade black to ^24.0.0

Update dependency coverage-badge to v1.1.2

• Schedule: ["at any time"]
• Branch name: renovate/coverage-badge-1.x-lockfile
• Merge into: main
• Upgrade coverage-badge to 1.1.2

Update dependency shellingham to v1.5.4

• Schedule: ["at any time"]
• Branch name: renovate/shellingham-1.x
• Merge into: main
• Upgrade shellingham to ==1.5.4

Update actions/cache action to v3.4.3

• Schedule: ["at any time"]
• Branch name: renovate/actions-cache-3.x
• Merge into: main
• Upgrade actions/cache to v3.4.3

Update actions/setup-python action to v4.9.1

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-python-4.x
• Merge into: main
• Upgrade actions/setup-python to v4.9.1

Update dependency bandit to v1.8.6

• Schedule: ["at any time"]
• Branch name: renovate/bandit-1.x-lockfile
• Merge into: main
• Upgrade bandit to 1.8.6

Update dependency click to v8.2.1

• Schedule: ["at any time"]
• Branch name: renovate/click-8.x
• Merge into: main
• Upgrade click to ==8.2.1

Update dependency coverage to v7.10.2

• Schedule: ["at any time"]
• Branch name: renovate/coverage-7.x-lockfile
• Merge into: main
• Upgrade coverage to 7.10.2

Update dependency isort to v5.13.2

• Schedule: ["at any time"]
• Branch name: renovate/isort-5.x-lockfile
• Merge into: main
• Upgrade isort to 5.13.2

Update dependency mypy to ^1.0.1

• Schedule: ["at any time"]
• Branch name: renovate/mypy-1.x
• Merge into: main
• Upgrade mypy to ^1.0.1

Update dependency pre-commit to v2.21.0

• Schedule: ["at any time"]
• Branch name: renovate/pre-commit-2.x-lockfile
• Merge into: main
• Upgrade pre-commit to 2.21.0

Update dependency pygments to v2.19.2

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

Update dependency pylint to v2.17.7

• Schedule: ["at any time"]
• Branch name: renovate/pylint-2.x-lockfile
• Merge into: main
• Upgrade pylint to 2.17.7

Update dependency pytest to ^7.2.2

• Schedule: ["at any time"]
• Branch name: renovate/pytest-7.x
• Merge into: main
• Upgrade pytest to ^7.2.2

Update dependency pytest-cov to ^4.0.0

• Schedule: ["at any time"]
• Branch name: renovate/pytest-cov-4.x
• Merge into: main
• Upgrade pytest-cov to ^4.0.0

Update dependency pyupgrade to ^3.20.0

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

Update dependency rich to ^13.3.2

• Schedule: ["at any time"]
• Branch name: renovate/rich-13.x
• Merge into: main
• Upgrade rich to ^13.3.2

Update dependency typer to v0.16.0

• Schedule: ["at any time"]
• Branch name: renovate/typer-0.x
• Merge into: main
• Upgrade typer to ^0.16.0
• Upgrade typer to ==0.16.0

Update release-drafter/release-drafter action to v5.25.0

• Schedule: ["at any time"]
• Branch name: renovate/release-drafter-release-drafter-5.x
• Merge into: main
• Upgrade release-drafter/release-drafter to v5.25.0

Update actions/cache action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-cache-4.x
• Merge into: main
• Upgrade actions/cache to v4.2.3

Update actions/checkout action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: main
• Upgrade actions/checkout to v4

Update actions/first-interaction action to v2

• Schedule: ["at any time"]
• Branch name: renovate/actions-first-interaction-2.x
• Merge into: main
• Upgrade actions/first-interaction to v2

Update actions/setup-python action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-python-5.x
• Merge into: main
• Upgrade actions/setup-python to v5.6.0

Update dependency importlib_metadata to v8

• Schedule: ["at any time"]
• Branch name: renovate/importlib_metadata-8.x
• Merge into: main
• Upgrade importlib_metadata to ^8.0.0

Update dependency isort to v6

• Schedule: ["at any time"]
• Branch name: renovate/isort-6.x
• Merge into: main
• Upgrade isort to ^6.0.0

Update dependency mypy-extensions to v1

• Schedule: ["at any time"]
• Branch name: renovate/mypy-extensions-1.x
• Merge into: main
• Upgrade mypy-extensions to ^1.0.0

Update dependency pre-commit to v4

• Schedule: ["at any time"]
• Branch name: renovate/pre-commit-4.x
• Merge into: main
• Upgrade pre-commit to ^4.0.0

Update dependency pylint to v3

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

Update dependency pytest to v8

• Schedule: ["at any time"]
• Branch name: renovate/pytest-8.x
• Merge into: main
• Upgrade pytest to ^8.0.0

Update dependency pytest-cov to v6

• Schedule: ["at any time"]
• Branch name: renovate/pytest-cov-6.x
• Merge into: main
• Upgrade pytest-cov to ^6.0.0

Update dependency pytest-html to v4

• Schedule: ["at any time"]
• Branch name: renovate/pytest-html-4.x
• Merge into: main
• Upgrade pytest-html to ^4.0.0

Update dependency rich to v14

• Schedule: ["at any time"]
• Branch name: renovate/rich-14.x
• Merge into: main
• Upgrade rich to ^14.0.0
• Upgrade rich to ==14.1.0

Update dependency safety to v3

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

Update release-drafter/release-drafter action to v6

• Schedule: ["at any time"]
• Branch name: renovate/release-drafter-release-drafter-6.x
• Merge into: main
• Upgrade release-drafter/release-drafter to v6.1.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 PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Note

Free review on us!

CodeRabbit is offering free reviews until Tue Aug 05 2025 to showcase some of the refinements we've made.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Hello @renovate[bot], thank you for submitting a PR! We will respond as soon as possible.