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

Merged
merged 1 commit into from
May 24, 2020
Merged

Configure Renovate #86

merged 1 commit into from
May 24, 2020

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 5, 2020

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
  • 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
  • Update existing lock files only when package.json is modified
  • 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

🔡 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.


You have configured Renovate to use branch master as base branch.

What to Expect

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

Pin dependencies
Update dependency eslint-plugin-node to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-node-11.x
  • Merge into: master
  • Upgrade eslint-plugin-node to 11.1.0
Update dependency mocha to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/mocha-7.x
  • Merge into: master
  • Upgrade mocha to 7.1.1
Update dependency nyc to v15
  • Schedule: ["at any time"]
  • Branch name: renovate/nyc-15.x
  • Merge into: master
  • Upgrade nyc to 15.0.1
Update dependency prettier to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-2.x
  • Merge into: master
  • Upgrade prettier to 2.0.4
Update dependency puppeteer to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/puppeteer-2.x
  • Merge into: master
  • Upgrade puppeteer to 2.1.1
Update dependency puppeteer-core to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/puppeteer-core-2.x
  • Merge into: master
  • Upgrade puppeteer-core to ^2.0.0
Update dependency sinon to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/sinon-9.x
  • Merge into: master
  • Upgrade sinon to 9.0.1
Update dependency yargs to v15
  • Schedule: ["at any time"]
  • Branch name: renovate/yargs-15.x
  • Merge into: master
  • Upgrade yargs to ^15.0.0

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

@coveralls
Copy link

coveralls commented Apr 5, 2020

Pull Request Test Coverage Report for Build 302

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 89.183%

Totals Coverage Status
Change from base Build 300: 0.0%
Covered Lines: 980
Relevant Lines: 1051

💛 - Coveralls

@Munter Munter merged commit 5c59547 into master May 24, 2020
@Munter Munter deleted the renovate/configure branch May 24, 2020 20:11
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.

3 participants