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

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

Configure Renovate #25

wants to merge 1 commit into from

Conversation

titouanmathis
Copy link
Contributor

@titouanmathis titouanmathis commented May 7, 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)
  • .github/workflows/release.yml (github-actions)
  • .github/workflows/tests.yml (github-actions)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • 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.
  • Schedule for typical non-office hours (night time and weekends).
  • Require Dependency Dashboard approval for major updates.
  • Automerge patch upgrades if they pass tests.
  • Raise a PR first before any automerging.
  • Require all status checks to pass before any automerging.
  • Do not separate patch and minor upgrades into separate PRs for the same dependency.
  • Run lock file maintenance (updates) early Monday mornings.
  • Pin dependency versions for devDependencies and retain SemVer ranges for others.
  • Always widen peerDependencies SemVer ranges when updating, instead of replacing.
  • Enable Renovate Dependency Dashboard creation.
  • 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.
  • Weekly schedule on early Monday mornings.
  • Run Renovate on following schedule: before 4am on Monday

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to .github/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 8 Pull Requests:

Update actions/cache action to v4
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/actions-cache-4.x
  • Merge into: develop
  • Upgrade actions/cache to v4
Update actions/checkout action to v4
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: develop
  • Upgrade actions/checkout to v4
Update dependency pestphp/pest to v2
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/pestphp-pest-2.x
  • Merge into: develop
  • Upgrade pestphp/pest to ^2.0
Update dependency phpstan/phpstan to v1
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/major-phpstan-packages
  • Merge into: develop
  • Upgrade phpstan/phpstan to ^1.0.0
Update dependency spatie/pest-plugin-snapshots to v2
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/spatie-pest-plugin-snapshots-2.x
  • Merge into: develop
  • Upgrade spatie/pest-plugin-snapshots to ^2.0
Update dependency spatie/url to v2
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/spatie-url-2.x
  • Merge into: develop
  • Upgrade spatie/url to ^2.0
Update php-actions/composer action to v6
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/php-actions-composer-6.x
  • Merge into: develop
  • Upgrade php-actions/composer to v6
Lock file maintenance
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: develop
  • 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.


This PR has been generated by Renovate Bot.

Copy link

codecov bot commented May 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.61%. Comparing base (017006a) to head (59569aa).

Additional details and impacted files
@@            Coverage Diff             @@
##             develop      #25   +/-   ##
==========================================
  Coverage      96.61%   96.61%           
  Complexity        52       52           
==========================================
  Files              7        7           
  Lines            177      177           
==========================================
  Hits             171      171           
  Misses             6        6           
Flag Coverage Δ
unittests 96.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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.

None yet

2 participants