chore(release): release v2.4.2

[hacke2]

Types

• Other Changes

Background or solution

ChangeLog

Summary by CodeRabbit

• 新功能

  • 新增语言模块支持：arm、kcl-vscode-extension 和 linkerscript。

• 版本更新

  • 多个软件包的版本已从 2.4.1 更新至 2.4.2。
  • opensumi 引擎的版本已从 3.6.1 更新至 3.6.2。
  • 相关依赖的版本也已更新至 3.6.2。

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

概述

演练

这个拉取请求主要是更新了整个项目的版本号和依赖版本。具体来说，lerna.json 和多个 package.json 文件的版本从 2.4.1 更新到 2.4.2。同时，多个 OpenSumi 相关的依赖包版本也从 3.6.1 升级到 3.6.2。此外，还在 packages/core/typings/languages.d.ts 中添加了三个新的语言模块声明。

变更

文件路径	变更摘要
lerna.json	版本从 2.4.1 更新到 2.4.2
package.json 和多个子包的 package.json	版本更新到 2.4.2，OpenSumi 依赖版本升级到 3.6.2
packages/core/typings/languages.d.ts	新增三个语言模块声明：arm、kcl-vscode-extension、linkerscript
packages/toolkit/define.json	__OPENSUMI_VERSION__ 从 3.6.1 更新到 3.6.2
scripts/upgrade-opensumi.js	添加 await exec('node scripts/generate') 命令

可能相关的 PR

• feat: support configure inline diff style #122: 更新多个 package.json 中的 opensumi 引擎版本
• fix: fix editor tabbar style #132: 类似地更新 opensumi 引擎版本
• feat: update opensumi #144: 更新多个包的 opensumi 引擎版本
• feat: update opensumi #146: 继续更新 opensumi 引擎版本
• chore: add provider example #178: 更新 lerna.json 和多个 package.json 的版本
• chore(release): release v2.1.0 #196: 更新 lerna.json 和多个 package.json 的版本号
• feat: upgrade opensumi #203: 将 OpenSumi 引擎升级到 3.5.0 版本
• feat: upgrade opensumi to 3.6.0 #240: 将 OpenSumi 引擎升级到 3.6.0 版本
• chore: @opensumi/textmate-languages #241: 更新 @opensumi/textmate-languages 依赖版本

建议的审阅者

• bytemain

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 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 129fb68 and 6da5605.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (16)

• 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/core/typings/languages.d.ts (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)
• scripts/upgrade-opensumi.js (1 hunks)

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.