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(release): release v2.5.1 #267

Merged
merged 2 commits into from
Mar 6, 2025
Merged

chore(release): release v2.5.1 #267

merged 2 commits into from
Mar 6, 2025

Conversation

hacke2
Copy link
Member

@hacke2 hacke2 commented Mar 6, 2025

Types

  • 🧹 Chores

Background or solution

ChangeLog

Summary by CodeRabbit

  • Chores
    • 将平台多个模块的版本号从 2.4.4 升级到 2.5.1,统一了系统版本。
    • 更新部分关键依赖项,从稳定版本切换至预发布版本(由 3.7.1 调整为 3.7.2-next),以提升兼容性和整体稳定性。

Sorry, something went wrong.

@hacke2 hacke2 merged commit 755b8e1 into main Mar 6, 2025
4 checks passed
@hacke2 hacke2 deleted the v2.5 branch March 6, 2025 02:35
Copy link

coderabbitai bot commented Mar 6, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

本 PR 对项目中多个配置文件和包文件的版本号进行了统一更新。在 lerna.json 中,版本由 2.4.4 更新至 2.5.1;根目录的 package.json 更新了 opensumi 引擎版本,从 3.7.1 调整为 3.7.2-next-1741226843.0。各子包(如 cli、core、sumi-core 等)不仅进行了版本号提升,同时将 opensumi 相关依赖的版本也统一调整为 3.7.2-next-1741226843.0。此外,toolkit 模块中的定义文件也同步更新了变量值。

Changes

文件 变更摘要
lerna.json
packages/code-api/package.json
packages/code-service/package.json
packages/common/package.json
packages/i18n/package.json
packages/plugin/package.json
packages/registry/package.json
packages/startup/package.json
packages/toolkit/package.json
版本号由 2.4.4 更新至 2.5.1
package.json (根目录) 更新 opensumi 引擎版本,从 3.7.1 修改为 3.7.2-next-1741226843.0
packages/cli/package.json
packages/core/package.json
packages/sumi-core/package.json
版本由 2.4.4 更新至 2.5.1,并将 opensumi 相关依赖版本从 3.7.1 调整为 3.7.2-next-1741226843.0
(注:core 包涉及多个依赖的更新)
packages/toolkit/define.json 更新 __OPENSUMI_VERSION__ 变量,从 "3.7.1" 变更为 "3.7.2-next-1741226843.0"

Possibly related PRs

Suggested reviewers

  • Ricbet

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1a8a486 and f002c1e.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (14)
  • lerna.json (1 hunks)
  • package.json (1 hunks)
  • packages/cli/package.json (2 hunks)
  • packages/code-api/package.json (1 hunks)
  • packages/code-service/package.json (1 hunks)
  • packages/common/package.json (1 hunks)
  • packages/core/package.json (2 hunks)
  • packages/i18n/package.json (1 hunks)
  • packages/plugin/package.json (1 hunks)
  • packages/registry/package.json (1 hunks)
  • packages/startup/package.json (1 hunks)
  • packages/sumi-core/package.json (2 hunks)
  • packages/toolkit/define.json (1 hunks)
  • packages/toolkit/package.json (1 hunks)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
  • @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.

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.

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