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

chore: Configure Renovate #42

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

chore: Configure Renovate #42

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 11, 2023

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/ci.yml (github-actions)
  • .github/workflows/pkg.pr.new.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • docs/package.json (npm)
  • package.json (npm)
  • packages/core/package.json (npm)
  • playground/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 (except for nuget) 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.
  • Use curated list of recommended non-monorepo package groupings.
  • Group all minor and patch updates together.
  • Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.
  • Schedule automerge monthly.
  • Schedule monthly.
  • Automerge non-major upgrades for semver stable packages if they pass tests.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Run Renovate on following schedule: before 4am on the first day of the month

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

fix(deps): update @dcloudio
fix(deps): update dependency vue to ~3.5.0
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/all-minor-patch
  • Merge into: main
  • Upgrade vue to ~3.5.0
chore(deps): update dependency conventional-changelog-conventionalcommits to v8
fix(deps): update dependency @​vueuse/core to v11
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/vueuse-core-11.x
  • Merge into: main
  • Upgrade @vueuse/core to ^11.0.0
fix(deps): update dependency vue-i18n to v10
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/vue-i18n-10.x
  • Merge into: main
  • Upgrade vue-i18n to ^10.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 was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants