Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Configure Renovate #23

Merged
merged 1 commit into from
Jul 18, 2021
Merged

Configure Renovate #23

merged 1 commit into from
Jul 18, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 22, 2020

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

  • Dockerfile (dockerfile)
  • go.mod (gomod)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • 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 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • Ignore spring cloud 1.x releases
  • 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

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

Update github.com/dchest/uniuri commit hash to 7aecb25
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-dchest-uniuri-digest
  • Merge into: master
  • Upgrade github.com/dchest/uniuri to 7aecb25e1fe5a22533fab90a637a8f74a9cf7340
Update module github.com/prometheus/client_golang to v0.9.4
Update module github.com/zpeters/speedtest to v1.0.5
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-zpeters-speedtest-1.x
  • Merge into: master
  • Upgrade github.com/zpeters/speedtest to v1.0.5
Update module github.com/prometheus/common to v0.29.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-prometheus-common-0.x
  • Merge into: master
  • Upgrade github.com/prometheus/common to 8281fb2779ab057c7d90fec6b24ce8eb29edcc13
Update module github.com/prometheus/client_golang to v1

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

@nlamirault nlamirault merged commit b6c74cc into master Jul 18, 2021
@delete-merged-branch delete-merged-branch bot deleted the renovate/configure branch July 18, 2021 20:37
@nlamirault nlamirault self-assigned this Aug 24, 2021
@nlamirault nlamirault added kind/feature Categorizes issue or PR as related to a new feature lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/high After critical issues are fixed, these should be dealt with before any further issues status/review_needed The issue or PR needs to be reviewed labels Aug 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/high After critical issues are fixed, these should be dealt with before any further issues status/review_needed The issue or PR needs to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants