chore: Configure Renovate

[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/release.yml (github-actions)
• package.json (npm)
• packages/client/package.json (npm)
• packages/kit/package.json (npm)
• packages/plugin/package.json (npm)
• packages/shared/package.json (npm)
• packages/types/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 (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 for the first day of each month, before 4 AM.
• Schedule once a month on the first day of the month before 4 AM.
• 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: * 0-3 1 * *

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

chore(deps): update dependency vite to v5.2.14 [security]

• Branch name: renovate/npm-vite-vulnerability
• Merge into: main
• Upgrade vite to 5.2.14

chore(deps): update pnpm to v9.15.0 [security]

• Branch name: renovate/npm-pnpm-vulnerability
• Merge into: main
• Upgrade pnpm to 9.15.0

fix(deps): update dependency vue-i18n to v9.14.2 [security]

• Branch name: renovate/npm-vue-i18n-vulnerability
• Merge into: main
• Upgrade vue-i18n to 9.14.2

fix(deps): update @dcloudio

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/@dcloudio
• Merge into: main
• Upgrade @dcloudio/uni-app to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-app-harmony to 3.0.0-alpha-4010320240415001
• Upgrade @dcloudio/uni-app-plus to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-automator to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-cli-shared to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-components to 3.0.0-alpha-3000020210521001
• Upgrade @dcloudio/uni-h5 to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-alipay to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-baidu to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-jd to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-kuaishou to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-lark to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-qq to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-toutiao to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-weixin to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-mp-xhs to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-quickapp-webview to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-stacktracey to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/uni-vue-devtools to 3.0.0-alpha-4040220241217001
• Upgrade @dcloudio/vite-plugin-uni to 3.0.0-alpha-3000020210521001

fix(deps): update all non-major dependencies

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/all-minor-patch
• Merge into: main
• Upgrade @antfu/eslint-config to 2.27.3
• Upgrade @antfu/ni to ^0.23.0
• Upgrade @uni-helper/eslint-config to ^0.2.0
• Upgrade @uni-helper/vite-plugin-uni-components to ^0.2.0
• Upgrade @unocss/eslint-config to ^0.65.0
• Upgrade @unocss/eslint-plugin to ^0.65.0
• Upgrade @unocss/reset to ^0.65.0
• Upgrade @vue/tsconfig to ^0.7.0
• Upgrade pinia to 2.3.0
• Upgrade pnpm to 8.15.9
• Upgrade unocss to ^0.65.0
• Upgrade unplugin-auto-import to ^0.19.0
• Upgrade unplugin-vue-components to ^0.28.0
• Upgrade unplugin-vue-router to ^0.10.0
• Upgrade vite-plugin-inspect to ^0.10.0

chore(deps): update actions/checkout action to v4

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: main
• Upgrade actions/checkout to v4

chore(deps): update dependency @​antfu/eslint-config to v3

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/antfu-eslint-config-3.x
• Merge into: main
• Upgrade @antfu/eslint-config to 3.12.0

chore(deps): update dependency @​types/node to v22

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/node-22.x
• Merge into: main
• Upgrade @types/node to ^22.0.0

chore(deps): update dependency concurrently to v9

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/concurrently-9.x
• Merge into: main
• Upgrade concurrently to ^9.0.0

chore(deps): update dependency eslint to v9

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/major-eslint-monorepo
• Merge into: main
• Upgrade eslint to ^9.0.0

chore(deps): update dependency rimraf to v6

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/rimraf-6.x
• Merge into: main
• Upgrade rimraf to ^6.0.0

chore(deps): update dependency unbuild to v3

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/unbuild-3.x
• Merge into: main
• Upgrade unbuild to ^3.0.0

chore(deps): update dependency vite to v6

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/vite-6.x
• Merge into: main
• Upgrade vite to ^6.0.0

chore(deps): update dependency vitest to v2

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/major-vitest-monorepo
• Merge into: main
• Upgrade vitest to ^2.0.0

chore(deps): update dependency vue-tsc to v2

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/vue-tsc-2.x
• Merge into: main
• Upgrade vue-tsc to ^2.0.0

chore(deps): update pnpm to v9

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/pnpm-9.x
• Merge into: main
• Upgrade pnpm to 9.15.1

fix(deps): update dependency @​vueuse/core to v12

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/major-vueuse-monorepo
• Merge into: main
• Upgrade @vueuse/core to ^12.0.0

fix(deps): update dependency detect-port to v2

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/detect-port-2.x
• Merge into: main
• Upgrade detect-port to ^2.0.0

fix(deps): update dependency glob to v11

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/glob-11.x
• Merge into: main
• Upgrade glob to ^11.0.0

fix(deps): update dependency sirv to v3

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/sirv-3.x
• Merge into: main
• Upgrade sirv 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 was generated by Mend Renovate. View the repository job log.

[pull-request-size]

Hi there 👋

Using this App for a private organization repository requires a paid subscription.

You can click Edit your plan on the Pull Request Size GitHub Marketplace listing to upgrade.

If you are a non-profit organization or otherwise can not pay for such a plan, contact me by creating an issue

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.