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.

---

Detected Package Files

• Dockerfile (dockerfile)
• .github/workflows/codacy-analysis.yml (github-actions)
• .github/workflows/codeql-analysis.yml (github-actions)
• requirements.txt (pip_requirements)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• 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 directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

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

Update dependency SQLAlchemy to v1.4.49

• Schedule: ["at any time"]
• Branch name: renovate/sqlalchemy-1.x
• Merge into: main
• Upgrade SQLAlchemy to ==1.4.49

Update dependency bcrypt to v3.2.2

• Schedule: ["at any time"]
• Branch name: renovate/bcrypt-3.x
• Merge into: main
• Upgrade bcrypt to ==3.2.2

Update dependency aiohttp to v3.8.5

• Schedule: ["at any time"]
• Branch name: renovate/aiohttp-3.x
• Merge into: main
• Upgrade aiohttp to ==3.8.5

Update dependency aiohttp-session to v2.12.0

• Schedule: ["at any time"]
• Branch name: renovate/aiohttp-session-2.x
• Merge into: main
• Upgrade aiohttp-session to ==2.12.0

Update dependency asyncpg to v0.28.0

• Schedule: ["at any time"]
• Branch name: renovate/asyncpg-0.x
• Merge into: main
• Upgrade asyncpg to ==0.28.0

Update python Docker tag to v3.11

• Schedule: ["at any time"]
• Branch name: renovate/python-3.x
• Merge into: main
• Upgrade python to 3.11-slim-buster

Update actions/checkout action to v3

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-3.x
• Merge into: main
• Upgrade actions/checkout to v3

Update codacy/codacy-analysis-cli-action action to v4

• Schedule: ["at any time"]
• Branch name: renovate/codacy-codacy-analysis-cli-action-4.x
• Merge into: main
• Upgrade codacy/codacy-analysis-cli-action to v4.3.0

Update dependency SQLAlchemy to v2

• Schedule: ["at any time"]
• Branch name: renovate/sqlalchemy-2.x
• Merge into: main
• Upgrade SQLAlchemy to ==2.0.19

Update dependency bcrypt to v4

• Schedule: ["at any time"]
• Branch name: renovate/bcrypt-4.x
• Merge into: main
• Upgrade bcrypt to ==4.0.1

Update github/codeql-action action to v2

• Schedule: ["at any time"]
• Branch name: renovate/github-codeql-action-2.x
• Merge into: main
• Upgrade github/codeql-action to v2

🚸 Branch 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. View repository job log here.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.