Configure Renovate

[tjboller]

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

• .github/workflows/test.yml (github-actions)
• pyproject.toml (pep621)
• .pre-commit-config.yaml (pre-commit)

Configuration Summary

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

• Start dependency updates only once this onboarding PR 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.
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Rebase existing PRs any time the base branch has been updated.
• Preserve (but continue to upgrade) any existing SemVer ranges.
• Separate each major version of dependencies into individual branches/PRs.
• Raise PR when vulnerability alerts are detected.
• Weekly schedule on early Monday mornings (before 4 AM).
• 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.
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Rebase existing PRs any time the base branch has been updated.
• Preserve (but continue to upgrade) any existing SemVer ranges.
• Separate each major version of dependencies into individual branches/PRs.
• Raise PR when vulnerability alerts are detected.
• Weekly schedule on early Monday mornings (before 4 AM).
• 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.
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Rebase existing PRs any time the base branch has been updated.
• Preserve (but continue to upgrade) any existing SemVer ranges.
• Separate each major version of dependencies into individual branches/PRs.
• Raise PR when vulnerability alerts are detected.
• Weekly schedule on early Monday mornings (before 4 AM).
• Run Renovate on following schedule: * 0-3 * * 1

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

---

What to Expect

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

Update dependency kaleido to v0.2.1.post1

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/kaleido-0.x
• Merge into: main
• Upgrade kaleido to ==0.2.1.post1

Update pre-commit hook astral-sh/ruff-pre-commit to v0.12.9

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/astral-sh-ruff-pre-commit-0.x
• Merge into: main
• Upgrade astral-sh/ruff-pre-commit to v0.12.9

Update pre-commit hook astral-sh/uv-pre-commit to v0.8.11

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/astral-sh-uv-pre-commit-0.x
• Merge into: main
• Upgrade astral-sh/uv-pre-commit to 0.8.11

Update actions/cache action to v4

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/actions-cache-4.x
• Merge into: main
• Upgrade actions/cache to v4

Update actions/checkout action to v4

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: main
• Upgrade actions/checkout to v4

Update actions/checkout action to v5

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: main
• Upgrade actions/checkout to v5

Update actions/setup-python action to v5

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/actions-setup-python-5.x
• Merge into: main
• Upgrade actions/setup-python to v5

Update astral-sh/setup-uv action to v2

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/astral-sh-setup-uv-2.x
• Merge into: main
• Upgrade astral-sh/setup-uv to v2

Update astral-sh/setup-uv action to v3

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/astral-sh-setup-uv-3.x
• Merge into: main
• Upgrade astral-sh/setup-uv to v3

Update astral-sh/setup-uv action to v4

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/astral-sh-setup-uv-4.x
• Merge into: main
• Upgrade astral-sh/setup-uv to v4

Update astral-sh/setup-uv action to v5

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/astral-sh-setup-uv-5.x
• Merge into: main
• Upgrade astral-sh/setup-uv to v5

Update astral-sh/setup-uv action to v6

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/astral-sh-setup-uv-6.x
• Merge into: main
• Upgrade astral-sh/setup-uv to v6

Update dependency kaleido to v1

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/kaleido-1.x
• Merge into: main
• Upgrade kaleido to ==1.0.0

Update dependency plotly to v6

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/plotly-6.x
• Merge into: main
• Upgrade plotly to >=6,<7

Update dependency pre-commit to v4

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/pre-commit-4.x
• Merge into: main
• Upgrade pre-commit to >=4,<5

Update dependency pyarrow to v17

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/pyarrow-17.x
• Merge into: main
• Upgrade pyarrow to >=17,<18

Update dependency pyarrow to v18

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/pyarrow-18.x
• Merge into: main
• Upgrade pyarrow to >=18,<19

Update dependency pyarrow to v19

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/pyarrow-19.x
• Merge into: main
• Upgrade pyarrow to >=19,<20

Update dependency pyarrow to v20

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/pyarrow-20.x
• Merge into: main
• Upgrade pyarrow to >=20,<21

Update dependency pyarrow to v21

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/pyarrow-21.x
• Merge into: main
• Upgrade pyarrow to >=21,<22

Update dependency pytest to v8

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/pytest-8.x
• Merge into: main
• Upgrade pytest to >=8,<9

Update pre-commit hook pre-commit/pre-commit-hooks to v6

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/pre-commit-pre-commit-hooks-6.x
• Merge into: main
• Upgrade pre-commit/pre-commit-hooks to v6.0.0

Lock file maintenance

• Schedule: ["before 4am on monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

---

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

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Renovate Bot.