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

Merged
merged 2 commits into from May 5, 2019
Merged

Configure Renovate #273

merged 2 commits into from May 5, 2019

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 26, 2018

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 concurrent Renovate PRs at any time
  • Group monorepo packages together
  • Group all packages published by Apollo GraphQL together
  • Group all packages by Font Awesome together
  • Group all @Polymer packages together
  • Recommended groupings of packages, even if not published from same monorepo

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

chore(deps): pin dependencies
chore(deps): update dependency shelljs to v0.8.2
  • Schedule: "at any time"
  • Branch name: renovate/shelljs-0.x
  • Upgrade shelljs to 0.8.2
chore(deps): update dependency chai to v4
  • Schedule: "at any time"
  • Branch name: renovate/chai-4.x
  • Upgrade chai to 4.2.0
chore(deps): update dependency mock-git to v2
  • Schedule: "at any time"
  • Branch name: renovate/mock-git-2.x
  • Upgrade mock-git to 2.0.0
chore(deps): update dependency nyc to v13
  • Schedule: "at any time"
  • Branch name: renovate/nyc-13.x
  • Upgrade nyc to 13.1.0
chore(deps): update dependency standard to v12
  • Schedule: "at any time"
  • Branch name: renovate/standard-12.x
  • Upgrade standard to 12.0.1
fix(deps): update dependency chalk to v2
  • Schedule: "at any time"
  • Branch name: renovate/chalk-2.x
  • Upgrade chalk to 2.4.1
fix(deps): update dependency conventional-changelog to v2
  • Schedule: "at any time"
  • Branch name: renovate/conventional-changelog-2.x
  • Upgrade conventional-changelog to 2.0.3
fix(deps): update dependency conventional-recommended-bump to v4
fix(deps): update dependency figures to v2
  • Schedule: "at any time"
  • Branch name: renovate/figures-2.x
  • Upgrade figures to 2.0.0
fix(deps): update dependency yargs to v12
  • Schedule: "at any time"
  • Branch name: renovate/yargs-12.x
  • Upgrade yargs to 12.0.2

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See: prHourlyLimit.


❓ If you have any questions, try reading the Docs, particularly the Getting Started section.
Also, you can post questions about your config in Renovate's Config Help repository.


This PR has been generated by Renovate Bot. View repository job log here.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f4d2cda on renovate/configure into e5c99f6 on master.

@bcoe bcoe closed this Nov 1, 2018
@bcoe bcoe reopened this May 5, 2019
@bcoe bcoe merged commit bf41474 into master May 5, 2019
@bcoe bcoe deleted the renovate/configure branch May 5, 2019 04:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants