chore: update deps

[oasis-cloud]

更新鸿蒙版本号

Summary by CodeRabbit

• 新特性
  • 更新了多个依赖项的版本，确保与最新的 Taro 版本兼容。
• 修复
  • 通过更新依赖项，潜在地解决了已知的错误和问题。
• 文档
  • 更新了项目的 package.json 文件以反映最新的依赖项和版本。

[coderabbitai]

Walkthrough

此拉取请求对@nutui/nutui-react和@nutui/nutui-taro-demo的package.json文件进行了更新，主要是依赖项版本的更改。@nutui/nutui-react的版本已增至3.0.0-beta.5，而多个与Taro相关的依赖项版本已从4.0.8-beta.0更新至4.0.8-beta.1。此外，@nutui/nutui-taro-demo中的多个依赖项也进行了类似的版本更新。同时，scripts/harmony/clone-jdharmony.js脚本中的branch变量的值也进行了调整。

Changes

文件路径	更改摘要
packages/nutui-react/package.json	版本更新至3.0.0-beta.5，多个Taro相关依赖项版本从4.0.8-beta.0更新至4.0.8-beta.1。
packages/nutui-taro-demo/package.json	更新@jdtaro/plugin-platform-jdharmony-cpp版本至0.1.4-alpha.2，多个Taro相关依赖项版本更新至4.0.8-beta.1。
scripts/harmony/clone-jdharmony.js	branch变量的值从'master-cpp'更新为'feat_jdharmonycpp'，当args[0] === 'cpp'时。

Possibly related PRs

• feat(progress): 四端适配 #2325: 该PR涉及更新package.json中的Taro依赖项，重点与主PR一致。
• fix: 重新安装依赖会出现依赖包的错误 #2424: 此PR解决依赖管理问题，与主PR中对Taro依赖项的更新相关。
• feat(navbar): 多端适配，demo icon使用占位符 #2594: 该PR更新了src/config.json文件，包括组件的版本更新，与主PR的依赖项更新相关。
• chore: remove rn's, and update taro version #2731: 此PR将Taro依赖项更新至更高版本，与主PR中的版本更新直接相关。
• chore: fix icon svg #2742: 此PR更新了@nutui/icons-react-taro的版本，与主PR中的依赖项更新相关。
• feat(Icon): icon harmony adaptation #2788: 此PR更新了多个组件的版本，与主PR中的依赖项更新相关。
• chore(ci): update branch #2792: 此PR更新了CI工作流中的分支名称，可能间接与主PR中的依赖项更新相关。

Suggested labels

size/XXL

Suggested reviewers

• xiaoyatong

Poem

🐇 在代码的草地上，
依赖更新如春风，
Taro版本齐飞舞，
让我们一起欢腾！
新的功能在前方，
兔子跳跃不再慌。
代码世界更辉煌！ 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9f7ca55 and ff9a220.

📒 Files selected for processing (1)

• scripts/harmony/clone-jdharmony.js (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• scripts/harmony/clone-jdharmony.js

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.98%. Comparing base (0a4bb29) to head (ff9a220).
Report is 2 commits behind head on feat_v3.x.

Additional details and impacted files

@@            Coverage Diff             @@
##           feat_v3.x    #2811   +/-   ##
==========================================
  Coverage      83.98%   83.98%           
==========================================
  Files            220      220           
  Lines          17882    17882           
  Branches        2676     2676           
==========================================
  Hits           15019    15019           
  Misses          2858     2858           
  Partials           5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.