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

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

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 15, 2021

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 10 Pull Requests:

fix(deps): update dependency lodash to v4 [security]
  • Branch name: renovate/npm-lodash-vulnerability
  • Merge into: master
  • Upgrade lodash to ^4.0.0
chore(deps): update dependency fibrous to ^0.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/fibrous-0.x
  • Merge into: master
  • Upgrade fibrous to ^0.4.0
chore(deps): update dependency node to 0.12
  • Schedule: ["at any time"]
  • Branch name: renovate/node-0.x
  • Merge into: master
  • Upgrade node to 0.12
chore(deps): update dependency chai to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/chai-5.x
  • Merge into: master
  • Upgrade chai to ~5.1.0
chore(deps): update dependency fibers to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/fibers-5.x
  • Merge into: master
  • Upgrade fibers to ^5.0.0
chore(deps): update dependency mocha to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/mocha-10.x
  • Merge into: master
  • Upgrade mocha to ~10.3.0
chore(deps): update dependency mocha-sinon to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/mocha-sinon-2.x
  • Merge into: master
  • Upgrade mocha-sinon to ~2.1.0
chore(deps): update dependency sinon-chai to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/sinon-chai-3.x
  • Merge into: master
  • Upgrade sinon-chai to ^3.0.0
fix(deps): update dependency lru-cache to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/lru-cache-10.x
  • Merge into: master
  • Upgrade lru-cache to ^10.0.0
fix(deps): update dependency npm-registry-client to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/npm-registry-client-8.x
  • Merge into: master
  • Upgrade npm-registry-client to ^8.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 from d299391 to 93b0cb4 Compare September 4, 2021 06:53
@renovate renovate bot force-pushed the renovate/configure branch from 93b0cb4 to 1315225 Compare June 26, 2022 10:18
@renovate renovate bot force-pushed the renovate/configure branch from 1315225 to dcc7d92 Compare March 22, 2023 19:47
@renovate renovate bot force-pushed the renovate/configure branch from dcc7d92 to a60ac3d Compare December 4, 2023 23:54
@renovate renovate bot force-pushed the renovate/configure branch from a60ac3d to 8f371f9 Compare December 15, 2023 17:29
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