Configure Renovate #1

Merged
cdamian merged 0 commits from refs/pull/1/head into main 2026-06-12 22:33:00 +02:00
cdamian commented 2026-06-12 20:28:52 +02:00 (Migrated from codeberg.org)

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

  • .forgejo/workflows/build.yml (github-actions)
  • pyproject.toml (poetry)
  • 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
  • Disable semantic prefixes for commit messages and PR titles.
  • Shared Renovate preset for all cdamian repos. Referenced as local>cdamian/renovate.

What to Expect

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

Update dependency click to >=8.4.1
  • Schedule: ["at any time"]
  • Branch name: renovate/click-8.x
  • Merge into: main
  • Upgrade click to >=8.4.1
Update dependency mypy to >=1.20.2
  • Schedule: ["at any time"]
  • Branch name: renovate/mypy-1.x
  • Merge into: main
  • Upgrade mypy to >=1.20.2
Update dependency pip-audit to >=2.10.1
  • Schedule: ["at any time"]
  • Branch name: renovate/pip-audit-2.x
  • Merge into: main
  • Upgrade pip-audit to >=2.10.1
Update dependency pytest to >=8.4.2
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-8.x
  • Merge into: main
  • Upgrade pytest to >=8.4.2
Update dependency requests to >=2.34.2
  • Schedule: ["at any time"]
  • Branch name: renovate/requests-2.x
  • Merge into: main
  • Upgrade requests to >=2.34.2
Update dependency ruff to >=0.15.17
  • Schedule: ["at any time"]
  • Branch name: renovate/ruff-0.x
  • Merge into: main
  • Upgrade ruff to >=0.15.17
Update dependency tox to >=4.55.1
  • Schedule: ["at any time"]
  • Branch name: renovate/tox-4.x
  • Merge into: main
  • Upgrade tox to >=4.55.1
Update dependency mypy to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/mypy-2.x
  • Merge into: main
  • Upgrade mypy to >=2.1.0
Update dependency pytest to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-9.x
  • Merge into: main
  • Upgrade pytest to >=9.0.3
Update https://code.forgejo.org/actions/checkout action to v6

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

Welcome to [Renovate](https://github.com/renovatebot/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](https://docs.renovatebot.com/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 * `.forgejo/workflows/build.yml` (github-actions) * `pyproject.toml` (poetry) * `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 - Disable semantic prefixes for commit messages and PR titles. - Shared Renovate preset for all cdamian repos. Referenced as `local>cdamian/renovate`. --- ### What to Expect With your current configuration, Renovate will create 10 Pull Requests: <details> <summary>Update dependency click to >=8.4.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/click-8.x` - Merge into: `main` - Upgrade [click](https://github.com/pallets/click) to `>=8.4.1` </details> <details> <summary>Update dependency mypy to >=1.20.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/mypy-1.x` - Merge into: `main` - Upgrade [mypy](https://github.com/python/mypy) to `>=1.20.2` </details> <details> <summary>Update dependency pip-audit to >=2.10.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/pip-audit-2.x` - Merge into: `main` - Upgrade [pip-audit](https://github.com/pypa/pip-audit) to `>=2.10.1` </details> <details> <summary>Update dependency pytest to >=8.4.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/pytest-8.x` - Merge into: `main` - Upgrade [pytest](https://github.com/pytest-dev/pytest) to `>=8.4.2` </details> <details> <summary>Update dependency requests to >=2.34.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/requests-2.x` - Merge into: `main` - Upgrade [requests](https://github.com/psf/requests) to `>=2.34.2` </details> <details> <summary>Update dependency ruff to >=0.15.17</summary> - Schedule: ["at any time"] - Branch name: `renovate/ruff-0.x` - Merge into: `main` - Upgrade [ruff](https://github.com/astral-sh/ruff) to `>=0.15.17` </details> <details> <summary>Update dependency tox to >=4.55.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/tox-4.x` - Merge into: `main` - Upgrade [tox](https://github.com/tox-dev/tox) to `>=4.55.1` </details> <details> <summary>Update dependency mypy to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/mypy-2.x` - Merge into: `main` - Upgrade [mypy](https://github.com/python/mypy) to `>=2.1.0` </details> <details> <summary>Update dependency pytest to v9</summary> - Schedule: ["at any time"] - Branch name: `renovate/pytest-9.x` - Merge into: `main` - Upgrade [pytest](https://github.com/pytest-dev/pytest) to `>=9.0.3` </details> <details> <summary>Update https://code.forgejo.org/actions/checkout action to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/https-code.forgejo.org-actions-checkout-6.x` - Merge into: `main` - Upgrade [https://code.forgejo.org/actions/checkout](https://code.forgejo.org/actions/checkout) to `v6` </details> 🚸 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`](https://docs.renovatebot.com/configuration-options/#prhourlylimit) for details. --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-config-hash:830ef01f8203a36a10cc1f6703597f6556cc39f880d4963842e1c98ced58b968-->
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
christof/fitimport!1
No description provided.