Configure Renovate
Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.
Detected Package Files
-
composer.json
(composer) -
.github/workflows/php.yml
(github-actions)
Configuration Summary
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 andchore
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.
- If automerging, push the new commit directly to the base branch (no MR).
- Update lint packages automatically if tests pass.
- Automerge
patch
upgrades if they pass tests. - Update testing packages automatically if tests pass.
- Update
@types/*
packages automatically if tests pass. - Disable Renovate Dependency Dashboard creation.
- Disable
major
updates. - Do not renovate
peerDependencies
versions/ranges. - Disable
digest
and Git hash updates. - Remove hourly and concurrent rate limits.
- Apply label
dependencies
to MRs. - Run lock file maintenance (updates) early Monday mornings.
- Pin dependency versions for
devDependencies
and retain SemVer ranges for others. - Wait for branch tests to pass or fail before creating the MR.
- Removes rate limit for MR creation per hour.
- Remove limit for open MRs at any time.
- Rebase existing MRs any time the base branch has been updated.
- Use semantic prefixes for commit messages and MR titles.
- Raise MR when vulnerability alerts are detected with label
security
. - Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.
- Apply crowd-sourced workarounds for known problems with packages.
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): lock file maintenance
- Schedule: ["before 4am on Monday"]
- Branch name:
renovate/lock-file-maintenance
- Merge into:
master
- Regenerate lock files to use latest dependency versions
This MR has been generated by Renovate Bot.