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.

📚 See our Reading List for relevant documentation you may be interested in reading.

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

---

Detected Package Files

• composer.json (composer)
• .github/workflows/format_php.yml (github-actions)
• .github/workflows/psalm.yml (github-actions)
• renovate.json (renovate-config)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• 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 (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
• Run lock file maintenance (updates) early Monday mornings.
• Group all minor and patch updates together.
• Separate each major version of dependencies into individual branches/PRs.
• Do not separate patch and minor upgrades into separate PRs for the same dependency.
• 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.
• Raise PR when vulnerability alerts are detected.
• Evaluate schedules according to timezone UTC.
• Append Signed-off-by: to signoff Git commits.
• Apply label dependencies to PRs.
• Schedule during typical non-office hours on weekdays (i.e., 10 PM - 5 AM) and anytime on weekends.
• Default Renovate config for InteractionDesignFoundation repositories. Security-critical defaults: config:best-practices preset, OSV vulnerability alerts, pinned Docker and GitHub Action digests, weekly lockfile maintenance, sequential major release PRs, non-office-hours schedule.
• Run Renovate on following schedule: * 0-4,22-23 * * 1-5,* * * * 0,6

---

What to Expect

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

Pin dependencies

• Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Upgrade actions/cache to caa296126883cff596d87d8935842f9db880ef25
• Upgrade actions/checkout to df4cb1c069e1874edd31b4311f1884172cec0e10
• Upgrade shivammathur/setup-php to f3e473d116dcccaddc5834248c87452386958240

Update actions/cache action to v6

• Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
• Branch name: renovate/actions-cache-6.x
• Merge into: main
• Upgrade actions/cache to 55cc8345863c7cc4c66a329aec7e433d2d1c52a9

Update actions/checkout action to v7

• Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
• Branch name: renovate/actions-checkout-7.x
• Merge into: main
• Upgrade actions/checkout to 9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0

Update dependency phpunit/phpunit to v13

• Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
• Branch name: renovate/phpunit-phpunit-13.x
• Merge into: main
• Upgrade phpunit/phpunit to ^13.0

Lock file maintenance

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

🚸 PR 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.

---

This PR was generated by Mend Renovate. View the repository job log.