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

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

Configure Renovate #5

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 2, 2019

WhiteSource 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

  • __LEGACY/package.json (npm)
  • 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
  • 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
  • Ignore spring cloud 1.x releases
  • Ignore http4s digest-based 1.x milestones

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

Update dependency jquery to v3 [SECURITY]
  • Branch name: renovate/npm-jquery-vulnerability
  • Merge into: master
  • Upgrade jquery to 3.6.0
Pin dependencies
Update dependency periodicjs to v10.70.92
  • Schedule: ["at any time"]
  • Branch name: renovate/periodicjs-10.x
  • Merge into: master
  • Upgrade periodicjs to 10.70.92
Update Node.js to v14
  • Schedule: ["at any time"]
  • Branch name: renovate/node-14.x
  • Merge into: master
  • Upgrade node to ^14.0.0
Update dependency browserify to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/browserify-17.x
  • Merge into: master
  • Upgrade browserify to 17.0.0
Update dependency chai to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/chai-4.x
  • Merge into: master
  • Upgrade chai to 4.3.4
Update dependency chai-as-promised to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/chai-as-promised-7.x
  • Merge into: master
  • Upgrade chai-as-promised to 7.1.1
Update dependency coveralls to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/coveralls-3.x
  • Merge into: master
  • Upgrade coveralls to 3.1.0
Update dependency grunt-browserify to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/grunt-browserify-6.x
  • Merge into: master
  • Upgrade grunt-browserify to 6.0.0
Update dependency grunt-contrib-cssmin to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/grunt-contrib-cssmin-4.x
  • Merge into: master
  • Upgrade grunt-contrib-cssmin to 4.0.0
Update dependency grunt-contrib-jshint to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/grunt-contrib-jshint-3.x
  • Merge into: master
  • Upgrade grunt-contrib-jshint to 3.0.0
Update dependency grunt-contrib-uglify to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/grunt-contrib-uglify-5.x
  • Merge into: master
  • Upgrade grunt-contrib-uglify to 5.0.0
Update dependency grunt-coveralls to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/grunt-coveralls-2.x
  • Merge into: master
  • Upgrade grunt-coveralls to 2.0.0
Update dependency grunt-mocha-istanbul to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/grunt-mocha-istanbul-5.x
  • Merge into: master
  • Upgrade grunt-mocha-istanbul to 5.0.2
Update dependency mocha to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/mocha-8.x
  • Merge into: master
  • Upgrade mocha to 8.3.2
Update dependency semver to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/semver-7.x
  • Merge into: master
  • Upgrade semver to 7.3.5
Update dependency sinon to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/sinon-10.x
  • Merge into: master
  • Upgrade sinon to 10.0.0
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.6.0
Update dependency supertest to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/supertest-6.x
  • Merge into: master
  • Upgrade supertest to 6.1.3
Update dependency uglify-js to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/uglify-js-3.x
  • Merge into: master
  • Upgrade uglify-js to 3.13.3
Update dependency uglifyify to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/uglifyify-5.x
  • Merge into: master
  • Upgrade uglifyify to 5.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 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.

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.

1 participant