Based on the default config's presets, Renovate will:
Start dependency updates only once this onboarding MR 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 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.
Rebase existing MRs any time the base branch has been updated.
Use semantic prefixes for commit messages and MR titles.
If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
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 Merge 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 16 Merge Requests:
chore(deps): update dependency beautifulsoup4 to v4.12.3
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.
