docker-chromium-xvfb icon indicating copy to clipboard operation
docker-chromium-xvfb copied to clipboard

Configure Renovate

Open renovate[bot] opened this issue 4 years ago • 1 comments

Mend 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

  • images/base/Dockerfile (dockerfile)
  • images/js-onbuild/Dockerfile-8.x (dockerfile)
  • images/js-onbuild/Dockerfile-9.x (dockerfile)
  • images/js/Dockerfile-8.x (dockerfile)
  • images/js/Dockerfile-9.x (dockerfile)
  • images/python2-onbuild/Dockerfile (dockerfile)
  • images/python2/Dockerfile (dockerfile)
  • images/python3-onbuild/Dockerfile (dockerfile)
  • images/python3/Dockerfile (dockerfile)
  • samples/js/Dockerfile (dockerfile)
  • samples/python2/Dockerfile (dockerfile)
  • samples/python3/Dockerfile (dockerfile)
  • samples/js/package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

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

chore(deps): update dependency karma to v6 [security]
  • Branch name: renovate/npm-karma-vulnerability
  • Merge into: master
  • Upgrade karma to ^6.0.0
chore(deps): update dependency karma-chrome-launcher to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-chrome-launcher-3.x
  • Merge into: master
  • Upgrade karma-chrome-launcher to ^3.0.0
chore(deps): update dependency karma-qunit to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-qunit-4.x
  • Merge into: master
  • Upgrade karma-qunit to ^4.0.0
chore(deps): update markadams/chromium-xvfb-js docker tag to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/markadams-chromium-xvfb-js-9.x
  • Merge into: master
  • Upgrade markadams/chromium-xvfb-js to 9

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm 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 Mend Renovate. View repository job log here.

renovate[bot] avatar Jun 09 '20 08:06 renovate[bot]

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution. If your email is listed below, please ensure that you sign the CLA with the same email address. The following users still need to sign our CLA:❌renovate[bot]

Already signed the CLA? To re-check, try refreshing the page.

atlassian-cla-bot[bot] avatar Jun 09 '20 08:06 atlassian-cla-bot[bot]