Configure Renovate

[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

• 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
• Ignore http4s digest-based 1.x milestones
• Weekly schedule on early monday mornings
• Run Renovate on following schedule: before 3am on Monday

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

Update dependency jest to v23.6.0

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/jest-monorepo
• Merge into: master
• Upgrade jest to 23.6.0

Update dependency netlify-lambda to v1.6.3

• Branch name: renovate/netlify-packages
• Merge into: master
• Upgrade netlify-lambda to 1.6.3

Update dependency rimraf to v2.7.1

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/rimraf-2.x-lockfile
• Merge into: master
• Upgrade rimraf to 2.7.1

Update vue monorepo to v3.12.1

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/vue-monorepo
• Merge into: master
• Upgrade @vue/cli to 3.12.1
• Upgrade @vue/cli-plugin-babel to 3.12.1
• Upgrade @vue/cli-service to 3.12.1
• Upgrade @vue/cli-test-utils to 3.12.1

Update dependency jest to v26

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/major-jest-monorepo
• Merge into: master
• Upgrade jest to ^26.0.0

Update dependency netlify-lambda to v2

• Branch name: renovate/major-netlify-packages
• Merge into: master
• Upgrade netlify-lambda to 2.0.3

Update dependency rimraf to v3

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/rimraf-3.x
• Merge into: master
• Upgrade rimraf to ^3.0.0

Update vue monorepo to v4 (major)

• Schedule: ["before 3am on Monday"]
• Branch name: renovate/major-vue-monorepo
• Merge into: master
• Upgrade @vue/cli to ^4.0.0
• Upgrade @vue/cli-plugin-babel to ^4.0.0
• Upgrade @vue/cli-service to ^4.0.0
• Upgrade @vue/cli-test-utils to ^4.0.0

Lock file maintenance

• Schedule: ["before 5am on monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: master
• Regenerate lock files to use latest dependency versions

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

Renovate is disabled

Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.