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

Closed
wants to merge 1 commit into from
Closed

Configure Renovate #30

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 30, 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 20 Pull Requests:

Pin dependencies
Update dependency shelljs to v0.8.3
  • Schedule: "at any time"
  • Branch name: renovate/shelljs-0.x
  • Upgrade shelljs to 0.8.3
Update dependency babel-eslint to v10
  • Schedule: "at any time"
  • Branch name: renovate/babel-eslint-10.x
  • Upgrade babel-eslint to 10.0.1
Update dependency babel-loader to v8
  • Schedule: "at any time"
  • Branch name: renovate/babel-loader-8.x
  • Upgrade babel-loader to 8.0.6
Update dependency chai to v4
  • Schedule: "at any time"
  • Branch name: renovate/chai-4.x
  • Upgrade chai to 4.2.0
Update dependency coveralls to v3
  • Schedule: "at any time"
  • Branch name: renovate/coveralls-3.x
  • Upgrade coveralls to 3.0.3
Update dependency eslint to v5
  • Schedule: "at any time"
  • Branch name: renovate/eslint-5.x
  • Upgrade eslint to 5.16.0
Update dependency eslint-plugin-react to v7
  • Schedule: "at any time"
  • Branch name: renovate/eslint-plugin-react-7.x
  • Upgrade eslint-plugin-react to 7.13.0
Update dependency karma to v4
  • Schedule: "at any time"
  • Branch name: renovate/karma-4.x
  • Upgrade karma to 4.1.0
Update dependency karma-cli to v2
  • Schedule: "at any time"
  • Branch name: renovate/karma-cli-2.x
  • Upgrade karma-cli to 2.0.0
Update dependency karma-coveralls to v2
  • Schedule: "at any time"
  • Branch name: renovate/karma-coveralls-2.x
  • Upgrade karma-coveralls to 2.1.0
Update dependency karma-sauce-launcher to v2
  • Schedule: "at any time"
  • Branch name: renovate/karma-sauce-launcher-2.x
  • Upgrade karma-sauce-launcher to 2.0.2
Update dependency karma-webpack to v3
  • Schedule: "at any time"
  • Branch name: renovate/karma-webpack-3.x
  • Upgrade karma-webpack to 3.0.5
Update dependency mocha to v6
  • Schedule: "at any time"
  • Branch name: renovate/mocha-6.x
  • Upgrade mocha to 6.1.4
Update dependency react-hot-loader to v4
  • Schedule: "at any time"
  • Branch name: renovate/react-hot-loader-4.x
  • Upgrade react-hot-loader to 4.8.8
Update dependency semver to v6
  • Schedule: "at any time"
  • Branch name: renovate/semver-6.x
  • Upgrade semver to 6.1.1
Update dependency webpack to v4
  • Schedule: "at any time"
  • Branch name: renovate/webpack-4.x
  • Upgrade webpack to 4.32.2
Update dependency webpack-dev-middleware to v3
  • Schedule: "at any time"
  • Branch name: renovate/webpack-dev-middleware-3.x
  • Upgrade webpack-dev-middleware to 3.7.0
Update dependency webpack-dev-server to v3 [SECURITY]
  • Branch name: renovate/npm-webpack-dev-server-vulnerability
  • Upgrade webpack-dev-server to 3.4.1
Update react monorepo to v16 (major)
  • Schedule: "at any time"
  • Branch name: renovate/major-react-monorepo
  • Upgrade react to ^15.4.1 || ^16.0.0
  • Upgrade react to 16.8.6
  • Upgrade react-dom to ^15.4.1 || ^16.0.0
  • Upgrade react-dom to 16.8.6

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

@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.296% when pulling b131f6c on renovate/configure into 497e7d7 on master.

@tanem tanem closed this May 31, 2019
@renovate
Copy link
Author

renovate bot commented May 31, 2019

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

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

3 participants