chore: Configure Renovate

[renovate-adamcik]

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 renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

Detected Package Files

• .github/workflows/cleanup.yml (github-actions)
• .github/workflows/workflow.yml (github-actions)
• flake.nix (nix)
• pyproject.toml (pep621)
• 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
• 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
• 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.
• Schedule once a month on the first day of the month before 4 AM.
• Run Renovate on following schedule: * 0-3 1 * *

---

What to Expect

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

chore(deps): pin dependencies

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/manager-digest-updates
• Merge into: main
• Upgrade actions/checkout to 11d5960a326750d5838078e36cf38b85af677262
• Upgrade cachix/cachix-action to 3ba601ff5bbb07c7220846facfa2cd81eeee15a1

fix(deps): update pep621 patch updates

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/pep621-patch-updates
• Merge into: main
• Upgrade lxml to ==6.1.1
• Upgrade psycopg2 to ==2.9.12

fix(deps): update pep621 minor updates

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/pep621-minor-updates
• Merge into: main
• Upgrade opentelemetry-api to ==1.44.0
• Upgrade opentelemetry-exporter-otlp-proto-http to ==1.44.0
• Upgrade opentelemetry-sdk to ==1.44.0
• Upgrade python to >=3.14,<3.15
• Upgrade reportlab to ==4.5.1

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

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

chore(deps): update cachix/cachix-action action to v17

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/cachix-cachix-action-17.x
• Merge into: main
• Upgrade cachix/cachix-action to 5f2d7c5294214f71b873db4b969586b980625e71

chore(deps): update dependency django-stubs to v6

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/django-stubs-6.x
• Merge into: main
• Upgrade django-stubs to ~=6.0.9

chore(deps): update dependency ipython to v9

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

fix(deps): update dependency django to v6

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/django-6.x
• Merge into: main
• Upgrade Django to ~=6.1.0

fix(deps): update dependency django-debug-toolbar to v7

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/django-debug-toolbar-7.x
• Merge into: main
• Upgrade django-debug-toolbar to ~=7.0.0

fix(deps): update dependency reportlab to v5

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

chore(deps): lock file maintenance

• Schedule: ["* 0-5 1-7 * 6"]
• 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 has been generated by Mend Renovate CLI.