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

---

Detected Package Files

• Dockerfile (dockerfile)
• .github/workflows/i18n.yml (github-actions)
• .github/workflows/publish-docker.yaml (github-actions)
• .github/workflows/release.yml (github-actions)
• .github/workflows/tests.yaml (github-actions)
• pyproject.toml (pep621)
• .pre-commit-config.yaml (pre-commit)
• .python-version (pyenv)
• 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
• Enable the pre-commit manager.
• Use semantic prefixes for commit messages and PR titles.
• If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
• Disable semantic commit scope for all commits and PR titles.
• Renovate policy shared by the authlib organization repositories.
• Run Renovate on following schedule: * * 1 * *

---

What to Expect

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

chore: update dependency setuptools to v83 [security]

• Branch name: renovate/pypi-setuptools-vulnerability
• Merge into: main
• Upgrade setuptools to 83.0.0

chore: update patch updates

• Schedule: ["* * 1 * *"]
• Branch name: renovate/patch-updates
• Merge into: main
• Upgrade codespell-project/codespell to v2.4.3
• Upgrade pytest-iam to 0.2.6
• Upgrade python-dotenv to 1.2.4

chore: update dependency updates

• Schedule: ["* * 1 * *"]
• Branch name: renovate/dependency-updates
• Merge into: main
• Upgrade astral-sh/ruff-pre-commit to v0.16.10
• Upgrade authlib to 1.8.0
• Upgrade beautifulsoup4 to 4.15.0
• Upgrade cachelib to 0.17.0
• Upgrade prek to 0.5.5
• Upgrade pyinstaller to 6.22.3
• Upgrade pytest to 9.1.1
• Upgrade requests to 2.34.2
• Upgrade tox-uv to 1.36.1

chore: update dependency updates (major)

• Schedule: ["* * 1 * *"]
• Branch name: renovate/major-dependency-updates
• Merge into: main
• Upgrade actions/checkout to v7
• Upgrade actions/download-artifact to v8
• Upgrade actions/setup-python to v7
• Upgrade actions/upload-artifact to v7
• Upgrade astral-sh/setup-uv to v10.2.0
• Upgrade docker/build-push-action to v7
• Upgrade docker/login-action to v4
• Upgrade docker/metadata-action to v6
• Upgrade docker/setup-buildx-action to v4
• Upgrade softprops/action-gh-release to v3

chore: lock file maintenance

• Schedule: ["* * 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. Security update Pull Request is not subject to this limit and will be created straight away.

---

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