Based on the default config's presets, Renovate will:
Start dependency updates only once this onboarding MR is merged
Separate major versions of dependencies into individual branches/MRs
Do not separate patch and minor upgrades into separate MRs for the same dependency
Upgrade to unstable versions only if the existing version is unstable
Raise MRs immediately (after branch is created)
If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
Keep existing branches updated even when not scheduled
Disable automerging feature - wait for humans to merge all MRs
Ignore node_modules, bower_components, vendor and various test/tests directories
Autodetect whether to pin dependencies or maintain ranges
Rate limit MR creation to a maximum of two per hour
Limit to maximum 20 open MRs at any time
Group known monorepo packages together
Use curated list of recommended non-monorepo package groupings
Ignore spring cloud 1.x releases
Ignore http4s digest-based 1.x milestones
Use node versioning for @types/node
Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
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 1 Merge Request:
chore(deps): update craig-day/compute-tag action to v13
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.
RenovateBot authored