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

• dev-requirements.txt (pip_requirements)
• 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
• 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.

🔡 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 12 Pull Requests:

Update dependency Sphinx to v1.8.6

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

Update dependency coverage to v4.5.4

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

Update dependency flake8 to v3.9.2

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

Update dependency flake8-bugbear to v19.8.0

• Schedule: ["at any time"]
• Branch name: renovate/flake8-bugbear-19.x
• Merge into: master
• Upgrade flake8-bugbear to ==19.8.0

Update dependency mypy to v0.991

• Schedule: ["at any time"]
• Branch name: renovate/mypy-0.x
• Merge into: master
• Upgrade mypy to ==0.991

Update dependency pre-commit to v1.21.0

• Schedule: ["at any time"]
• Branch name: renovate/pre-commit-1.x
• Merge into: master
• Upgrade pre-commit to ==1.21.0

Update dependency Sphinx to v7

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

Update dependency coverage to v7

• Schedule: ["at any time"]
• Branch name: renovate/coverage-7.x
• Merge into: master
• Upgrade coverage to ==7.3.3

Update dependency flake8 to v6

• Schedule: ["at any time"]
• Branch name: renovate/flake8-6.x
• Merge into: master
• Upgrade flake8 to ==6.1.0

Update dependency flake8-bugbear to v23

• Schedule: ["at any time"]
• Branch name: renovate/flake8-bugbear-23.x
• Merge into: master
• Upgrade flake8-bugbear to ==23.12.2

Update dependency mypy to v1

• Schedule: ["at any time"]
• Branch name: renovate/mypy-1.x
• Merge into: master
• Upgrade mypy to ==1.7.1

Update dependency pre-commit to v3

• Schedule: ["at any time"]
• Branch name: renovate/pre-commit-3.x
• Merge into: master
• Upgrade pre-commit to ==3.6.0

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

[pull-request-quantifier-deprecated]

This PR has 4 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +4 -0
Percentile : 1.6%

Total files changed: 1

Change summary by file extension:
.json : +4 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.