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 Jun 9, 2020

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

  • .github/workflows/on-push.yml (github-actions)
  • 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 10 Pull Requests:

Update dependency yaml to v2.2.2 [SECURITY]
  • Branch name: renovate/npm-yaml-vulnerability
  • Merge into: master
  • Upgrade yaml to 2.2.2
Update dependency @​actions/core to v1.10.1
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-core-1.x-lockfile
  • Merge into: master
  • Upgrade @actions/core to 1.10.1
Update dependency husky to v8.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-8.x-lockfile
  • Merge into: master
  • Upgrade husky to 8.0.3
Update dependency @​vercel/ncc to ^0.38.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vercel-ncc-0.x
  • Merge into: master
  • Upgrade @vercel/ncc to ^0.38.0
Update dependency eslint to v8.55.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-8.x-lockfile
  • Merge into: master
  • Upgrade eslint to 8.55.0
Update dependency jest to v29.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-monorepo
  • Merge into: master
  • Upgrade jest to 29.7.0
Update dependency nock to v13.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/nock-13.x-lockfile
  • Merge into: master
  • Upgrade nock to 13.4.0
Update dependency node-fetch to v2.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/node-fetch-2.x-lockfile
  • Merge into: master
  • Upgrade node-fetch to 2.7.0
Update dependency jest-junit to v16
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-junit-16.x
  • Merge into: master
  • Upgrade jest-junit to ^16.0.0
Update dependency node-fetch to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/node-fetch-3.x
  • Merge into: master
  • Upgrade node-fetch to ^3.0.0

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

@atlassian-cla-bot
Copy link

atlassian-cla-bot bot commented Jun 9, 2020

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.

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.

0 participants