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 #48

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Configure Renovate #48

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 14, 2023

Mend 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/ci.yml (github-actions)
  • .github/workflows/craft-release.yaml (github-actions)
  • .github/workflows/set-milestone-on-pr.yaml (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.
  • 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 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.
  • Always widen peerDependencies SemVer ranges when updating, instead of replacing.
  • Rebase existing PRs any time the base branch has been updated.
  • Removes rate limit for PR creation per hour.
  • Remove limit for open PRs at any time.
  • Group PHPStan packages together.
  • Run Renovate on following schedule: * 6-22/3 * * 1-5,* 12-23/3 * * 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 6 Pull Requests:

Update github/super-linter Docker tag to v2.2.2
  • Schedule: ["* 6-22/3 * * 1-5","* 12-23/3 * * 0,6"]
  • Branch name: renovate/github-super-linter-2.x
  • Merge into: master
  • Upgrade github/super-linter to v2.2.2
Update actions/cache action to v3
  • Schedule: ["* 6-22/3 * * 1-5","* 12-23/3 * * 0,6"]
  • Branch name: renovate/actions-cache-3.x
  • Merge into: master
  • Upgrade actions/cache to v3
Update actions/checkout action to v4
  • Schedule: ["* 6-22/3 * * 1-5","* 12-23/3 * * 0,6"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to v4
Update dependency psr/log to v3
  • Schedule: ["* 6-22/3 * * 1-5","* 12-23/3 * * 0,6"]
  • Branch name: renovate/psr-log-3.x
  • Merge into: master
  • Upgrade psr/log to ^2 || ^3
Update dependency wyrihaximus/async-test-utilities to v7
  • Schedule: ["* 6-22/3 * * 1-5","* 12-23/3 * * 0,6"]
  • Branch name: renovate/wyrihaximus-async-test-utilities-7.x
  • Merge into: master
  • Upgrade wyrihaximus/async-test-utilities to ^4.2.0 || ^7.0.0
Update github/super-linter Docker tag to v5
  • Schedule: ["* 6-22/3 * * 1-5","* 12-23/3 * * 0,6"]
  • Branch name: renovate/github-super-linter-5.x
  • Merge into: master
  • Upgrade github/super-linter to v5.0.0

❓ 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from WyriHaximus as a code owner January 14, 2023 14:58
@github-actions github-actions bot added this to the 3.1.0 milestone Jan 14, 2023
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.

None yet

0 participants