Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 4, 2025

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)
  • renovate.json (renovate-config-presets)

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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Do not separate patch and minor upgrades into separate PRs for the same dependency.
  • Rebase existing PRs any time the base branch has been updated.
  • Add the renovate/ prefix to all branch names.
  • Use semantic prefixes for commit messages and PR titles.
  • Use semantic commit scope deps for all commits and PR titles.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Update $schema version in biome.json configuration files.
  • Group various lint packages together.
  • Schedule automerge daily before 4 AM.
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Schedule for weekends.
  • Group PostCSS packages together.
  • 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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Do not separate patch and minor upgrades into separate PRs for the same dependency.
  • Rebase existing PRs any time the base branch has been updated.
  • Add the renovate/ prefix to all branch names.
  • Use semantic prefixes for commit messages and PR titles.
  • Use semantic commit scope deps for all commits and PR titles.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Update $schema version in biome.json configuration files.
  • Group various lint packages together.
  • Schedule automerge daily before 4 AM.
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Schedule for weekends.
  • Group PHP Illuminate packages together.
  • Group PHPStan packages together.
  • Run Renovate on following schedule: * * * * 0,6

🔡 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 1 Pull Request:

chore(deps): lock file maintenance
  • Schedule: ["before 4am on monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • 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.


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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants