Configure Renovate

[renovate]

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/continuous-integration.yml (github-actions)
• .github/workflows/docs-build.yml (github-actions)
• .github/workflows/release-on-milestone-closed.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Automerge patch and minor upgrades if they pass tests.
• If automerging, push the new commit directly to the base branch (no PR).
• Rebase existing PRs any time the base branch has been updated.
• Disable semantic prefixes for commit messages and PR titles.
• 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

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

Update actions/checkout action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: 2.22.x
• Upgrade actions/checkout to v4

Update dependency phpunit/phpunit to v11

• Schedule: ["at any time"]
• Branch name: renovate/phpunit-phpunit-11.x
• Merge into: 2.22.x
• Upgrade phpunit/phpunit to ^11.0.0

Lock file maintenance

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/lock-file-maintenance
• Merge into: 2.22.x
• Regenerate lock files to use latest dependency versions

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

---

❓ 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.