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

Merged
merged 1 commit into from Feb 3, 2021
Merged

Configure Renovate #259

merged 1 commit into from Feb 3, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 2, 2021

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

  • package.json (npm)

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 12 Pull Requests:

chore(deps): pin dependencies
chore(deps): update dependency tmp to v0.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/tmp-0.x
  • Merge into: master
  • Upgrade tmp to 0.2.1
chore(deps): update dependency browserify to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/browserify-17.x
  • Merge into: master
  • Upgrade browserify to 17.0.0
chore(deps): update dependency chromedriver to v88
  • Schedule: ["at any time"]
  • Branch name: renovate/chromedriver-88.x
  • Merge into: master
  • Upgrade chromedriver to 88.0.0
chore(deps): update dependency cross-env to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/cross-env-7.x
  • Merge into: master
  • Upgrade cross-env to 7.0.3
chore(deps): update dependency eslint to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-7.x
  • Merge into: master
  • Upgrade eslint to 7.19.0
chore(deps): update dependency istanbul-lib-instrument to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-istanbuljs-monorepo
  • Merge into: master
  • Upgrade istanbul-lib-instrument to 4.0.3
chore(deps): update dependency jsdom to v16
  • Schedule: ["at any time"]
  • Branch name: renovate/jsdom-16.x
  • Merge into: master
  • Upgrade jsdom to 16.4.0
chore(deps): update dependency mocha to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/mocha-8.x
  • Merge into: master
  • Upgrade mocha to 8.2.1
chore(deps): update dependency nyc to v15
  • Schedule: ["at any time"]
  • Branch name: renovate/nyc-15.x
  • Merge into: master
  • Upgrade nyc to 15.1.0
chore(deps): update dependency sinon to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/sinon-9.x
  • Merge into: master
  • Upgrade sinon to 9.2.4
chore(deps): update dependency tape to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/tape-5.x
  • Merge into: master
  • Upgrade tape to 5.1.1

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

@rpl rpl merged commit 24bab25 into master Feb 3, 2021
@rpl rpl deleted the renovate/configure branch February 3, 2021 17:33
@renovate
Copy link
Contributor Author

renovate bot commented Jan 10, 2023

Renovate is disabled

Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.

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

2 participants