chore: Configure Renovate #6

Merged
alpha-nerd merged 1 commit from renovate/configure into main 2026-05-09 22:16:33 +02:00
Collaborator

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/publish.yml (github-actions)
  • requirements.txt (pip_requirements)
  • 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

What to Expect

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

fix(deps): update dependency cryptography to v46.0.7
  • Schedule: ["at any time"]
  • Branch name: renovate/cryptography-46.x
  • Merge into: main
  • Upgrade cryptography to ==46.0.7
chore(deps): update python docker tag to v3.14
  • Schedule: ["at any time"]
  • Branch name: renovate/python-3.x
  • Merge into: main
  • Upgrade python to 3.14-bookworm
fix(deps): update dependency anyio to v4.13.0
  • Schedule: ["at any time"]
  • Branch name: renovate/anyio-4.x
  • Merge into: main
  • Upgrade anyio to ==4.13.0
fix(deps): update dependency idna to v3.13
  • Schedule: ["at any time"]
  • Branch name: renovate/idna-3.x
  • Merge into: main
  • Upgrade idna to ==3.13
fix(deps): update dependency certifi to v2026
  • Schedule: ["at any time"]
  • Branch name: renovate/certifi-2026.x
  • Merge into: main
  • Upgrade certifi to ==2026.4.22
fix(deps): update dependency cryptography to v48
  • Schedule: ["at any time"]
  • Branch name: renovate/cryptography-48.x
  • Merge into: main
  • Upgrade cryptography to ==48.0.0
fix(deps): update dependency pycparser to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/pycparser-3.x
  • Merge into: main
  • Upgrade pycparser to ==3.0

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/publish.yml` (github-actions) * `requirements.txt` (pip_requirements) * `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 --- ### What to Expect With your current configuration, Renovate will create 7 Pull Requests: <details> <summary>fix(deps): update dependency cryptography to v46.0.7</summary> - Schedule: ["at any time"] - Branch name: `renovate/cryptography-46.x` - Merge into: `main` - Upgrade [cryptography](https://github.com/pyca/cryptography) to `==46.0.7` </details> <details> <summary>chore(deps): update python docker tag to v3.14</summary> - Schedule: ["at any time"] - Branch name: `renovate/python-3.x` - Merge into: `main` - Upgrade python to `3.14-bookworm` </details> <details> <summary>fix(deps): update dependency anyio to v4.13.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/anyio-4.x` - Merge into: `main` - Upgrade [anyio](https://github.com/agronholm/anyio) to `==4.13.0` </details> <details> <summary>fix(deps): update dependency idna to v3.13</summary> - Schedule: ["at any time"] - Branch name: `renovate/idna-3.x` - Merge into: `main` - Upgrade [idna](https://github.com/kjd/idna) to `==3.13` </details> <details> <summary>fix(deps): update dependency certifi to v2026</summary> - Schedule: ["at any time"] - Branch name: `renovate/certifi-2026.x` - Merge into: `main` - Upgrade [certifi](https://github.com/certifi/python-certifi) to `==2026.4.22` </details> <details> <summary>fix(deps): update dependency cryptography to v48</summary> - Schedule: ["at any time"] - Branch name: `renovate/cryptography-48.x` - Merge into: `main` - Upgrade [cryptography](https://github.com/pyca/cryptography) to `==48.0.0` </details> <details> <summary>fix(deps): update dependency pycparser to v3</summary> - Schedule: ["at any time"] - Branch name: `renovate/pycparser-3.x` - Merge into: `main` - Upgrade [pycparser](https://github.com/eliben/pycparser) to `==3.0` </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:d57cb80be9b9b62b0be96ded34a1e2baeb716c53ce2b4310f2822c6a33f25b56-->
renovate-bot added the
dependencies
label 2026-05-09 22:14:27 +02:00
renovate-bot added 1 commit 2026-05-09 22:14:28 +02:00
alpha-nerd merged commit e44fb7f45a into main 2026-05-09 22:16:33 +02:00
Sign in to join this conversation.
No description provided.