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

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

Configure Renovate #4

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 30, 2019

Mend 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)
  • .travis.yml (travis)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

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

Update dependency debug to v4.3.1 [SECURITY]
  • Branch name: renovate/npm-debug-vulnerability
  • Merge into: master
  • Upgrade debug to 4.3.1
Update dependency @​tuya/tuya-connector-nodejs to v2.1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/tuya-tuya-connector-nodejs-2.x-lockfile
  • Merge into: master
  • Upgrade @tuya/tuya-connector-nodejs to 2.1.2
Update dependency delay to v4.4.1
  • Schedule: ["at any time"]
  • Branch name: renovate/delay-4.x-lockfile
  • Merge into: master
  • Upgrade delay to 4.4.1
Update dependency xo to ^0.56.0
  • Schedule: ["at any time"]
  • Branch name: renovate/xo-0.x
  • Merge into: master
  • Upgrade xo to ^0.56.0
Update dependency delay to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/delay-6.x
  • Merge into: master
  • Upgrade delay to ^6.0.0

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

@renovate renovate bot force-pushed the renovate/configure branch 2 times, most recently from 50f715d to a876945 Compare January 31, 2020 22:43
@renovate renovate bot force-pushed the renovate/configure branch from a876945 to 8542c4d Compare August 27, 2020 03:56
@renovate renovate bot force-pushed the renovate/configure branch from 8542c4d to a25801d Compare July 19, 2021 02:15
@renovate renovate bot force-pushed the renovate/configure branch from a25801d to ed71083 Compare November 17, 2021 08:12
@renovate renovate bot force-pushed the renovate/configure branch from ed71083 to 3f7e8a6 Compare January 1, 2022 19:14
@renovate renovate bot force-pushed the renovate/configure branch from 3f7e8a6 to 796a9a7 Compare June 26, 2022 07:30
@renovate renovate bot force-pushed the renovate/configure branch from 796a9a7 to c96a9d3 Compare December 15, 2023 05:13
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.

0 participants