Configure Renovate

[renovate]

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

🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request.

---

Detected Package Files

• .github/workflows/check-ricochet-ids.yml (github-actions)
• python/dash-hello/pyproject.toml (pep621)
• python/fastapi-hello/pyproject.toml (pep621)
• python/flask-hello/pyproject.toml (pep621)
• python/python-sleep/pyproject.toml (pep621)
• python/quarto-py-hello/pyproject.toml (pep621)
• python/streamlit-hello/pyproject.toml (pep621)
• python/dash-hello/.python-version (pyenv)
• python/fastapi-hello/.python-version (pyenv)
• python/flask-hello/.python-version (pyenv)
• python/python-sleep/.python-version (pyenv)
• python/quarto-py-hello/.python-version (pyenv)
• python/streamlit-hello/.python-version (pyenv)
• renovate.json (renovate-config-presets)

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.
• 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
• Run lock file maintenance (updates) early Monday mornings.
• Schedule automerge daily before 4 AM.
• Schedule daily before 4 AM.
• If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
• Enable the pre-commit manager.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Enable Renovate configuration migration PRs when needed.
• Run Renovate on following schedule: * 0-3 * * *

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

chore(deps): update python docker tag

• Schedule: ["* 0-3 * * *"]
• Branch name: renovate/python-3.x
• Merge into: main
• Upgrade python to 3.14
• Upgrade python to 3.14.3

chore(deps): update actions/checkout action to v6

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

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

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