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

Merged
merged 3 commits into from
Sep 29, 2024
Merged

Configure Renovate #1234

merged 3 commits into from
Sep 29, 2024

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 22, 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/build.yml (github-actions)
  • .github/workflows/examples-branch.yml (github-actions)
  • .github/workflows/examples-master.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
  • 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.
  • Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.
  • Schedule daily.
  • Run Renovate on following schedule: before 4am

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

Update dependency @​cucumber/gherkin to v29
  • Schedule: ["before 4am"]
  • Branch name: renovate/cucumber-gherkin-29.x
  • Merge into: master
  • Upgrade @cucumber/gherkin to ^29.0.0
Update dependency @​cucumber/messages to v26
  • Schedule: ["before 4am"]
  • Branch name: renovate/cucumber-messages-26.x
  • Merge into: master
  • Upgrade @cucumber/messages to ^26.0.0
Update dependency chalk to v5
  • Schedule: ["before 4am"]
  • Branch name: renovate/chalk-5.x
  • Merge into: master
  • Upgrade chalk to ^5.0.0

🚸 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 was generated by Mend Renovate. View the repository job log.

renovate bot and others added 2 commits September 22, 2024 14:51
Trying this (Renovate) out for the first time.
@badeball badeball merged commit a16cf61 into master Sep 29, 2024
47 of 52 checks passed
@renovate renovate bot deleted the renovate/configure branch September 29, 2024 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant