Based on the default config's presets, Renovate will:
Start dependency updates only once this onboarding PR 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.
Weekly schedule on early Monday mornings.
Group all minor and patch updates together.
Run Renovate on following schedule: before 4am on Monday
🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json5 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 2 Pull Requests:
chore(deps): update actions/checkout action to v4
- Schedule: ["before 4am on Monday"]
- Branch name: `renovate/actions-checkout-4.x`
- Merge into: `main`
- Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v4`
chore(deps): update actions/setup-python action to v4
- Schedule: ["before 4am on Monday"]
- Branch name: `renovate/actions-setup-python-4.x`
- Merge into: `main`
- Upgrade [actions/setup-python](https://togithub.com/actions/setup-python) to `v4`
❓ 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.
DT-5590 <- Put your own jira issue here by setting the
prHeadervalue in your renovate configWelcome 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/build.yml(github-actions).github/workflows/dependency-review.yml(github-actions)docs/requirements.txt(pip_requirements)Pipfile(pipenv)setup.cfg(setup-cfg)Configuration Summary
Based on the default config's presets, Renovate will:
fixfor dependencies andchorefor all others if semantic commits are in use.node_modules,bower_components,vendorand various test/tests directories.minorandpatchupdates together.🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the
renovate.json5in 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 2 Pull Requests:
chore(deps): update actions/checkout action to v4
- Schedule: ["before 4am on Monday"] - Branch name: `renovate/actions-checkout-4.x` - Merge into: `main` - Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v4`chore(deps): update actions/setup-python action to v4
- Schedule: ["before 4am on Monday"] - Branch name: `renovate/actions-setup-python-4.x` - Merge into: `main` - Upgrade [actions/setup-python](https://togithub.com/actions/setup-python) to `v4`❓ 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 the Coveo Renovate Bot