chore: Configure Renovate

[khepri-bot]

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/pr-checks.yaml (github-actions)
• pyproject.toml (pep621)
• .python-version (pyenv)

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.
• 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 PRs 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.
• Run lock file maintenance (updates) early Monday mornings.
• Managed by khepri-deps/renovate — global config provides weekly Monday schedule, 14-day release cooldown, and vulnerability alert bypass.
• Run Renovate on following schedule: * 0-5 * * 1

🔡 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 3 Pull Requests:

fix(deps): update all non-major dependencies

• Schedule: ["* 0-5 * * 1"]
• Branch name: renovate/all-non-major-dependencies
• Merge into: main
• Upgrade astral-sh/setup-uv to d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86
• Pin click to ==8.3.1
• Pin jinja2 to ==3.1.6
• Pin pydantic to ==2.12.5
• Pin python to ==3.14.3
• Pin pyyaml to ==6.0.3
• Pin rich to ==14.3.3

chore(deps): update all major dependencies to v6

• Schedule: ["* 0-5 * * 1"]
• Branch name: renovate/all-major-dependencies
• Merge into: main
• Upgrade actions/checkout to de0fac2e4500dabe0009e67214ff5f5447ce83dd
• Upgrade astral-sh/setup-uv to d0cc045d04ccac9d8b7881df0226f9e82c39688e

chore(deps): lock file maintenance

• Schedule: ["* 0-3 * * 1"]
• 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.

---

This PR has been generated by Renovate Bot.