Configure Renovate #1

Merged
renovate[bot] merged 1 commits from renovate/configure into master 2021-02-10 23:12:32 +03:00
renovate[bot] commented 2021-02-09 02:06:54 +03:00 (Migrated from github.com)

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

  • .github/workflows/pr.yml (github-actions)
  • .github/workflows/push.yml (github-actions)

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

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

Update actions/setup-go action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-go-2.x
  • Merge into: master
  • Upgrade actions/setup-go to v2
Update golangci/golangci-lint-action action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/golangci-golangci-lint-action-2.x
  • Merge into: master
  • Upgrade golangci/golangci-lint-action to v2

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.

[![WhiteSource Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) Welcome to [Renovate](https://togithub.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. :vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. --- ### Detected Package Files * `.github/workflows/pr.yml` (github-actions) * `.github/workflows/push.yml` (github-actions) ### 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 <code>fix</code> for dependencies and <code>chore</code> 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 :abcd: 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 2 Pull Requests: <details> <summary>Update actions/setup-go action to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-setup-go-2.x` - Merge into: `master` - Upgrade [actions/setup-go](https://togithub.com/actions/setup-go) to `v2` </details> <details> <summary>Update golangci/golangci-lint-action action to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/golangci-golangci-lint-action-2.x` - Merge into: `master` - Upgrade [golangci/golangci-lint-action](https://togithub.com/golangci/golangci-lint-action) to `v2` </details> --- :question: Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://togithub.com/renovatebot/renovate/discussions). --- This PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#{{platform}}/{{repository}}).
Sign in to join this conversation.
No description provided.