Based on the default config's presets, Renovate will:
Start dependency updates only once this onboarding PR is merged
Enable Renovate Dependency Dashboard creation.
Ignore node_modules, bower_components, vendor and various test/tests directories.
Automerge patch and minor upgrades if they pass tests.
If automerging, push the new commit directly to the base branch (no PR).
Wait for branch tests to pass or fail before creating the PR.
Rebase existing PRs any time the base branch has been updated.
Separate major versions of dependencies into individual branches/PRs.
Do not separate patch and minor upgrades into separate PRs for the same dependency.
Raise PR when vulnerability alerts are detected.
Evaluate schedules according to timezone UTC.
Append Signed-off-by: to signoff Git commits.
Apply label renovate to PRs.
Group all minor and patch updates together.
Default configuration for repositories in the Laminas organisation
🔡 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 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:
Update actions/checkout action to v3
- Schedule: ["at any time"]
- Branch name: `renovate/actions-checkout-3.x`
- Merge into: `2.1.x`
- Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v3`
Lock file maintenance
- Schedule: ["before 2am"]
- Branch name: `renovate/lock-file-maintenance`
- Merge into: `2.1.x`
- Regenerate lock files to use latest dependency versions
❓ 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.
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
composer.json(composer).github/workflows/release-on-milestone-closed.yml(github-actions)Configuration Summary
Based on the default config's presets, Renovate will:
node_modules,bower_components,vendorand various test/tests directories.patchandminorupgrades if they pass tests.majorversions of dependencies into individual branches/PRs.patchandminorupgrades into separate PRs for the same dependency.UTC.Signed-off-by:to signoff Git commits.renovateto PRs.minorandpatchupdates together.🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the
renovate.jsonin 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:
Update actions/checkout action to v3
- Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-3.x` - Merge into: `2.1.x` - Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v3`Lock file maintenance
- Schedule: ["before 2am"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `2.1.x` - Regenerate lock files to use latest dependency versions❓ 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.
Read more information about the use of Renovate Bot within Laminas.