Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Renovate #5

Merged
merged 1 commit into from
Nov 1, 2024
Merged

Configure Renovate #5

merged 1 commit into from
Nov 1, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2024

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)
  • docker-compose-mysql.yml (docker-compose)
  • .github/workflows/continous-integration.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 LM-Commons 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 2 Pull Requests:

Update dependency phpunit/phpunit to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/phpunit-phpunit-11.x
  • Merge into: 1.0.x
  • Upgrade phpunit/phpunit to ^11.0
Lock file maintenance
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: 1.0.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 LM-Commons.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot added the renovate label Nov 1, 2024
@visto9259 visto9259 merged commit 553fea9 into 1.0.x Nov 1, 2024
13 checks passed
@visto9259 visto9259 deleted the renovate/configure branch November 1, 2024 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant