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/ci.yml (github-actions)
• .github/workflows/pkg.pr.new.yml (github-actions)
• .github/workflows/release.yml (github-actions)
• 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 4 Pull Requests:

fix(deps): update @dcloudio

• Schedule: ["before 4am on the first day of the month"]
• Branch name: renovate/@dcloudio
• Merge into: main
• Upgrade @dcloudio/uni-app to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-app-plus to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-automator to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-cli-shared to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-components to 3.0.0-alpha-3000020210521001
• Upgrade @dcloudio/uni-h5 to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-mp-alipay to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-mp-baidu to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-mp-kuaishou to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-mp-lark to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-mp-qq to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-mp-toutiao to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-mp-weixin to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-quickapp-webview to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/uni-stacktracey to 3.0.0-alpha-4030220241101001
• Upgrade @dcloudio/vite-plugin-uni to 3.0.0-alpha-3000020210521001

chore(deps): update all non-major dependencies

• Schedule: ["before 4am on the first day of the month"]
• Branch name: renovate/all-minor-patch
• Merge into: main
• Upgrade taze to ^0.18.0
• Upgrade typescript to ~5.6.0
• Upgrade vue to ~3.5.0

chore(deps): update dependency conventional-changelog-conventionalcommits to v8

• Schedule: ["before 4am on the first day of the month"]
• Branch name: renovate/conventional-changelog-conventionalcommits-8.x
• Merge into: main
• Upgrade conventional-changelog-conventionalcommits to ^8.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.

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