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

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

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 3, 2022

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

  • vim/bundle/Command-T/Gemfile (bundler)

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 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.

🔡 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 dependency mechanize to v2 [SECURITY]
  • Branch name: renovate/rubygems-mechanize-vulnerability
  • Merge into: master
  • Upgrade mechanize to 2.8.5
Update dependency rake to v12 [SECURITY]
  • Branch name: renovate/rubygems-rake-vulnerability
  • Merge into: master
  • Upgrade rake to 12.3.3
Update dependency rr to v1.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/rr-1.x-lockfile
  • Merge into: master
  • Upgrade rr to 1.2.1
Update dependency rspec to v2.99.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rspec-2.x-lockfile
  • Merge into: master
  • Upgrade rspec to 2.99.0
Update dependency rr to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/rr-3.x-lockfile
  • Merge into: master
  • Upgrade rr to 3.1.0
Update dependency rspec to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/rspec-3.x-lockfile
  • Merge into: master
  • Upgrade rspec to 3.12.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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/configure branch from 0d8ade4 to c49b93d Compare June 26, 2022 06:59
@renovate renovate bot force-pushed the renovate/configure branch from c49b93d to 4743623 Compare December 15, 2023 08:17
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.

0 participants