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

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

Configure Renovate #133

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 19, 2022

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)
  • .nvmrc (nvm)

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.
  • Group all minor and patch updates together.
  • If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
  • Default config for Meema repositories

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

chore(deps): update devdependency vite to v2.9.16 [security]
  • Branch name: renovate/npm-vite-vulnerability
  • Merge into: develop
  • Upgrade vite to 2.9.16
chore(deps): update all non-major dependencies
chore(deps): update dependency node to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/node-18.x
  • Merge into: develop
  • Upgrade node to 18.17
chore(deps): update devdependency @​heroicons/vue to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/heroicons-vue-2.x
  • Merge into: develop
  • Upgrade @heroicons/vue to ^2.0.18
chore(deps): update devdependency @​types/tailwindcss to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/tailwindcss-3.x
  • Merge into: develop
  • Upgrade @​types/tailwindcss to ^3.0.11
chore(deps): update devdependency @​vitejs/plugin-vue to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/vitejs-plugin-vue-4.x
  • Merge into: develop
  • Upgrade @vitejs/plugin-vue to ^4.2.3

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

@vercel
Copy link

vercel bot commented Apr 19, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
hoodratz ✅ Ready (Inspect) Visit Preview Apr 27, 2022 at 7:31AM (UTC)

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