chore: Configure Renovate

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

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

• .github/workflows/python-app.yml (github-actions)
• .github/workflows/python-publish.yml (github-actions)
• requirements.txt (pip_requirements)
• setup.py (pip_setup)

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.

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

---

What to Expect

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

chore(deps): update dependency sphinx-rtd-theme to v0.5.2

• Schedule: ["at any time"]
• Branch name: renovate/sphinx-rtd-theme-0.x
• Merge into: master
• Upgrade sphinx-rtd-theme to ==0.5.2

chore(deps): update dependency python to 3.13

• Schedule: ["at any time"]
• Branch name: renovate/python-3.x
• Merge into: master
• Upgrade python to 3.13

chore(deps): update dependency sphinx to v3.5.4

• Schedule: ["at any time"]
• Branch name: renovate/sphinx-3.x
• Merge into: master
• Upgrade Sphinx to ==3.5.4

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

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: master
• Upgrade actions/checkout to v5

chore(deps): update actions/setup-python action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-python-6.x
• Merge into: master
• Upgrade actions/setup-python to v6

chore(deps): update dependency coveralls to v4

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

chore(deps): update dependency sphinx to v8

• Schedule: ["at any time"]
• Branch name: renovate/sphinx-8.x
• Merge into: master
• Upgrade Sphinx to ==8.2.3

chore(deps): update dependency sphinx-rtd-theme to v3

• Schedule: ["at any time"]
• Branch name: renovate/sphinx-rtd-theme-3.x
• Merge into: master
• Upgrade sphinx-rtd-theme to ==3.0.2

🚸 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 was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

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