chore: 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.

📚 See our Reading List for relevant documentation you may be interested in reading.

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

---

Detected Package Files

• .github/workflows/ci.yml (github-actions)
• .github/workflows/deploy-docs.yml (github-actions)
• .github/workflows/zizmor_action.yml (github-actions)
• docs/requirements-docs.txt (pip_requirements)
• requirements-dev.txt (pip_requirements)
• requirements.txt (pip_requirements)
• pyproject.toml (poetry)
• .github/renovate.json (renovate-config)

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 Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.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
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Run lock file maintenance (updates) on the first day of each month.
• If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
• Schedule once a month on the first day of the month before 4 AM.
• Default freqtrade renovate config
• Run Renovate on following schedule: * 0-5 * * 4

---

What to Expect

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

chore(deps): update dependency ruff to v0.16.9

• Schedule: ["* 0-5 * * 4"]
• Branch name: renovate/python-dev-minor-patch
• Merge into: main
• Upgrade ruff to ==0.16.9

chore(deps): update dependency ta-lib to v0.8.1

• Schedule: ["* 0-5 * * 4"]
• Branch name: renovate/ta-lib
• Merge into: main
• Upgrade TA-Lib to ==0.8.1

chore(deps): update python non-major dependencies

• Schedule: ["* 0-5 * * 4"]
• Branch name: renovate/python-minor-patch
• Merge into: main
• Upgrade markdown to ==3.11
• Upgrade numpy to ==2.5.3

chore(deps): update dependency ubuntu to v26

• Schedule: ["* 0-5 * * 4"]
• Branch name: renovate/ubuntu-26.x
• Merge into: main
• Upgrade ubuntu to 26.04

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 was generated by Mend Renovate. View the repository job log.