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

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

Conversation

renovate-bot
Copy link

@renovate-bot renovate-bot commented Apr 24, 2022

WhiteSource 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

  • WORKSPACE (bazel)
  • scala/private/macros/scala_repositories.bzl (bazel)

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
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 10 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • Fix some problems with very old Maven commons versions
  • Ignore spring cloud 1.x releases
  • Ignore web3j 5.0.0 release
  • Ignore http4s digest-based 1.x milestones
  • Use node versioning for @types/node
  • Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
  • Do not upgrade from Alpine stable to edge

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


What to Expect

With your current configuration, Renovate will create 4 Pull Requests:

Update rules_cc digest to cb6d32e
  • Schedule: ["at any time"]
  • Branch name: renovate/rules_cc-digest
  • Merge into: master
  • Upgrade rules_cc to cb6d32e4d1ae29e20dd3328109d8cb7f8eccc9be
Update rules_proto digest to 3212323
  • Schedule: ["at any time"]
  • Branch name: renovate/rules_proto-digest
  • Merge into: master
  • Upgrade rules_proto to 3212323502e21b819ac4fbdd455cb227ad0f6394
Update dependency io_bazel_rules_go to v0.31.0
  • Schedule: ["at any time"]
  • Branch name: renovate/io_bazel_rules_go-0.x
  • Merge into: master
  • Upgrade io_bazel_rules_go to v0.31.0
Update dependency rules_java to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/rules_java-5.x
  • Merge into: master
  • Upgrade rules_java to 5.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam 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 WhiteSource Renovate. View repository job log here.

@renovate-bot renovate-bot force-pushed the renovate/configure branch 2 times, most recently from 5d9bb2c to 2884bcd Compare April 29, 2022 09:01
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.

2 participants