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

Merged
merged 1 commit into from May 3, 2019
Merged

Configure Renovate #21

merged 1 commit into from May 3, 2019

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 26, 2019

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 Configure Renovate 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)
  • Use renovate/ as prefix for all branch names
  • 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.


What to Expect

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

Pin dependencies
Update dependency chai to v4
  • Schedule: "at any time"
  • Branch name: renovate/chai-4.x
  • Upgrade chai to 4.2.0
Update dependency eslint to v5
  • Schedule: "at any time"
  • Branch name: renovate/eslint-5.x
  • Upgrade eslint to 5.16.0
Update dependency mocha to v6
  • Schedule: "at any time"
  • Branch name: renovate/mocha-6.x
  • Upgrade mocha to 6.1.4

🚸 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 Renovate Bot. View repository job log here.

@CLAassistant
Copy link

CLAassistant commented Mar 26, 2019

CLA assistant check
All committers have signed the CLA.

@coveralls
Copy link

coveralls commented Mar 26, 2019

Coverage Status

Coverage remained the same at 69.811% when pulling 0a4117f on renovate/configure into c20457a on master.

@ivan-nginx ivan-nginx merged commit d6cac3c into master May 3, 2019
@delete-merged-branch delete-merged-branch bot deleted the renovate/configure branch May 3, 2019 07:31
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.

None yet

5 participants