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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Configure Renovate #1

wants to merge 2 commits into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 10, 2019

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

  • 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.
  • Evaluate schedules according to timezone Asia/Tokyo.

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

fix(deps): update patch updates (patch)
  • Schedule: ["at any time"]
  • Branch name: renovate/patch-patch-updates
  • Merge into: master
  • Upgrade almin to ^0.12.5
  • Upgrade cross-env to ^5.1.6
  • Upgrade espower-typescript to ^8.1.4
  • Upgrade mocha to ^5.0.5
chore(deps): update minor updates (minor)
  • Schedule: ["at any time"]
  • Branch name: renovate/minor-updates
  • Merge into: master
  • Upgrade @types/node to ^9.6.61
  • Upgrade almin to ^0.19.0
  • Upgrade cross-env to ^5.2.1
  • Upgrade mocha to ^5.2.0
  • Upgrade power-assert to ^1.6.1
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 espower-typescript to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/espower-typescript-10.x
  • Merge into: master
  • Upgrade espower-typescript to ^10.0.1
chore(deps): update dependency mocha to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/mocha-10.x
  • Merge into: master
  • Upgrade mocha to ^10.2.0
  • Upgrade @types/mocha to ^10.0.1

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

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.

2 participants