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

Merged
merged 2 commits into from
Jan 10, 2024
Merged

Configure Renovate #1

merged 2 commits into from
Jan 10, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 6, 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

  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/release-tag.yml (github-actions)
  • package.json (npm)
  • playground/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.
  • Weekly schedule on early Monday mornings.
  • Group all minor and patch updates together.
  • Run Renovate on following schedule: before 4am on Monday

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

chore(deps): update dependency vite to v5.0.5 [security]
  • Branch name: renovate/npm-vite-vulnerability
  • Merge into: main
  • Upgrade vite to 5.0.5
chore(deps): update all non-major dependencies
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/all-minor-patch
  • Merge into: main
  • Upgrade enquirer to ^2.4.1
  • Upgrade esno to ^0.17.0
  • Upgrade minimist to ^1.2.8
  • Upgrade node to >=14.21.3
  • Upgrade pnpm to 8.14.1
  • Upgrade prettier to ^2.8.8
  • Upgrade rollup to ^2.79.1
  • Upgrade semver to ^7.5.4
  • Upgrade source-map to ^0.7.4
  • Upgrade unbuild to ^0.9.4
  • Upgrade vitest to ^0.34.6
chore(deps): update dependency @​rollup/pluginutils to v5
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/rollup-pluginutils-5.x
  • Merge into: main
  • Upgrade @rollup/pluginutils to ^5.1.0
chore(deps): update dependency conventional-changelog-cli to v4
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/conventional-changelog-cli-4.x
  • Merge into: main
  • Upgrade conventional-changelog-cli to ^4.1.0
chore(deps): update dependency esno to v4
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/esno-4.x
  • Merge into: main
  • Upgrade esno to ^4.0.0
chore(deps): update dependency execa to v8
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/execa-8.x
  • Merge into: main
  • Upgrade execa to ^8.0.1
chore(deps): update dependency fs-extra to v11
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/fs-extra-11.x
  • Merge into: main
  • Upgrade fs-extra to ^11.2.0
  • Upgrade @types/fs-extra to ^11.0.4
chore(deps): update dependency prettier to v3
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/prettier-3.x
  • Merge into: main
  • Upgrade prettier to ^3.1.1
chore(deps): update dependency rollup to v4
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/rollup-4.x
  • Merge into: main
  • Upgrade rollup to ^4.9.4
chore(deps): update dependency slash to v5
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/slash-5.x
  • Merge into: main
  • Upgrade slash to ^5.1.0
chore(deps): update dependency unbuild to v2
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/unbuild-2.x
  • Merge into: main
  • Upgrade unbuild to ^2.0.0
chore(deps): update dependency vitest to v1
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: main
  • Upgrade vitest to ^1.1.3
chore(deps): update node.js to v20
  • Schedule: ["before 4am on Monday"]
  • Branch name: renovate/node-20.x
  • Merge into: main
  • Upgrade node to >=20.11.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.

@renovate renovate bot force-pushed the renovate/configure branch from 63249e9 to 95a0acd Compare March 22, 2023 21:46
@renovate renovate bot force-pushed the renovate/configure branch from 95a0acd to c43999a Compare December 15, 2023 17:39
@patak-dev patak-dev merged commit 17ddf64 into main Jan 10, 2024
2 checks passed
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