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

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

Configure Renovate #29

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

  • .github/workflows/npm-publish.yml (github-actions)
  • package.json (npm)

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 (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.
  • Schedule during typical non-office hours on weekdays (i.e., 10 PM - 5 AM) and anytime on 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 (before 4 AM).
  • Run Renovate on following schedule: * 0-3 * * 1

🔡 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 10 Pull Requests:

Update dependency browserslist to v4.16.5 [SECURITY]
  • Branch name: renovate/npm-browserslist-vulnerability
  • Merge into: master
  • Upgrade browserslist to 4.16.5
Pin dependencies
Update actions/checkout action to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to v4
Update actions/setup-node action to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: master
  • Upgrade actions/setup-node to v4
Update dependency @​studiometa/eslint-config to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/studiometa-eslint-config-4.x
  • Merge into: master
  • Upgrade @studiometa/eslint-config to ^4.0.0
Update dependency @​studiometa/prettier-config to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/studiometa-prettier-config-4.x
  • Merge into: master
  • Upgrade @studiometa/prettier-config to ^4.0.0
Update dependency eslint to v9
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: master
  • Upgrade eslint to ^9.0.0
Update dependency jest to v29
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: master
  • Upgrade jest to ^29.0.0
Update dependency prettier to v3
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/prettier-3.x
  • Merge into: master
  • Upgrade prettier to ^3.0.0
Lock file maintenance
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: master
  • 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.

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.

2 participants