Skip to content
This repository has been archived by the owner on Sep 28, 2021. It is now read-only.

Configure Renovate #1

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

Conversation

renovate-config-app-private[bot]
Copy link

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

  • package.json (npm)

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

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

Pin dependencies
  • Schedule: ["at any time"]
  • Branch name: private-renovatebot/pin-dependencies
  • Merge into: master
  • Pin jasmine to 2.9.0
  • Pin jshint to 2.9.5
Update dependency adm-zip to ^0.5.0
  • Schedule: ["at any time"]
  • Branch name: private-renovatebot/adm-zip-0.x
  • Merge into: master
  • Upgrade adm-zip to ^0.5.0
Update dependency jasmine to v2.99.0
  • Schedule: ["at any time"]
  • Branch name: private-renovatebot/jasmine-monorepo
  • Merge into: master
  • Upgrade jasmine to 2.99.0
Update dependency jshint to v2.12.0
  • Schedule: ["at any time"]
  • Branch name: private-renovatebot/jshint-2.x
  • Merge into: master
  • Upgrade jshint to 2.12.0
Update dependency cross-spawn to v7
  • Schedule: ["at any time"]
  • Branch name: private-renovatebot/cross-spawn-7.x
  • Merge into: master
  • Upgrade cross-spawn to ^7.0.0
Update dependency jasmine to v3
  • Schedule: ["at any time"]
  • Branch name: private-renovatebot/major-jasmine-monorepo
  • Merge into: master
  • Upgrade jasmine to 3.6.4

❓ 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 Renovate Bot.

@renovate-config-app-private renovate-config-app-private bot force-pushed the renovate/configure branch 15 times, most recently from 267ce5a to 125d7b2 Compare January 27, 2021 13:52
@renovate-config-app-private renovate-config-app-private bot force-pushed the renovate/configure branch 5 times, most recently from 5e328e8 to 2303188 Compare February 5, 2021 04:44
@renovate-config-app-private renovate-config-app-private bot force-pushed the renovate/configure branch 8 times, most recently from febd14c to cb37bb1 Compare February 13, 2021 04:42
@renovate-config-app-private renovate-config-app-private bot force-pushed the renovate/configure branch 2 times, most recently from b84ede1 to 1737690 Compare February 15, 2021 04:44
@renovate-config-app-private renovate-config-app-private bot force-pushed the renovate/configure branch 7 times, most recently from 9869827 to e08b0b5 Compare April 12, 2021 04:28
@renovate-config-app-private renovate-config-app-private bot force-pushed the renovate/configure branch 8 times, most recently from 5abe740 to 07f9a7b Compare April 20, 2021 04:30
@renovate-config-app-private renovate-config-app-private bot force-pushed the renovate/configure branch 8 times, most recently from 37d86eb to bef6f39 Compare April 28, 2021 04:29
@renovate-config-app-private renovate-config-app-private bot force-pushed the renovate/configure branch 5 times, most recently from cd54bdb to c163fa2 Compare May 3, 2021 04:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
0 participants