chore(release): release v3.7.1

[Ricbet]

Summary by CodeRabbit

• Chores
  • 全平台各模块及依赖版本更新至 3.7.1，内部构建和持续集成流程得到优化，整体系统稳定性与性能均有所提升。
• Bug Fixes
  • 改进了评论区的交互和展示逻辑，优化了隐藏功能，确保用户在使用评论功能时能获得更加流畅的体验。

[Ricbet]

/create-merge-commit

[opensumi]

Start merging the pull request

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

该 PR 在 CI 配置和代码基础设施上进行了两类变更。首先，在 GitHub Actions 的 e2e 流程中新增了安装 libsecret-1-dev 的步骤，并将上传构件的 action 版本从 v3 升级至 v4。其次，对多个包的版本号进行了统一更新（大部分从 3.7.0 或 3.6.4 提升至 3.7.1），同时对评论组件做了改进，包括调整 CommentsZoneWidget 的类型和构造函数参数、修改隐藏逻辑，以及在服务中由调用 thread.hideWidgetsByDispose() 改为 thread.hide()。

Changes

文件	更改描述
.github/workflows/e2e.yml	新增安装 libsecret-1-dev 的步骤；将 actions/upload-artifact 从 v3 升级到 v4。
lerna.json、packages/.../package.json、tools/.../package.json、 packages/types/manifest.json、packages/types/package.json	统一更新版本号，大部分从 "3.7.0"（或 "3.6.4"）提升至 "3.7.1"。
packages/comments/src/browser/comments-zone.view.tsx packages/comments/src/browser/comments.service.ts	修改 CommentsZoneWidget：调整 wrapperRoot 类型、公开构造函数参数及隐藏逻辑（由调用 super.dispose() 改为 super.hide()）；在 CommentsService 中将调用修改为 thread.hide()。

Sequence Diagram(s)

sequenceDiagram
    participant GH as GitHub Actions
    participant Checkout as 检出步骤
    participant LibSecret as 安装 libsecret-1-dev
    participant Node as Node.js 环境
    participant Upload as 上传构件 (v4)

    GH->>Checkout: 执行代码检出
    Checkout-->>GH: 完成检出
    GH->>LibSecret: 执行安装 libsecret-1-dev
    LibSecret-->>GH: 安装完成
    GH->>Node: 设置 Node.js 环境
    Node-->>GH: 环境就绪
    GH->>Upload: 上传测试结果

Loading

sequenceDiagram
    participant Service as CommentsService
    participant Widget as CommentsZoneWidget
    participant Base as 父类组件

    Service->>Widget: 调用 thread.hide()
    Widget->>Base: 执行 hide() 方法（调用 super.hide()）
    Base-->>Widget: 隐藏操作完成

Loading

Possibly related PRs

• chore(release): release v3.2.0 #3901: 涉及 lerna.json 的版本更新，与本次 PR 的版本管理变更在代码层面存在直接联系。
• chore(release): release v3.1.4 #3821: 同样针对多个 package.json 文件的版本号更新，虽然目标版本不同，但两者均涉及统一的版本管理。

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

yarn install v1.22.22
[1/4] Resolving packages...
warning eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning eslint > @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning eslint-import-resolver-typescript > glob@7.2.3: Glob versions prior to v9 are no longer supported
error Couldn't find any versions for "@opensumi/ide-dev-tool" that matches "workspace:*"
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f7b6e0e and 222d132.

📒 Files selected for processing (67)

• .github/workflows/e2e.yml (2 hunks)
• lerna.json (1 hunks)
• packages/addons/package.json (1 hunks)
• packages/ai-native/package.json (1 hunks)
• packages/collaboration/package.json (1 hunks)
• packages/comments/package.json (1 hunks)
• packages/comments/src/browser/comments-zone.view.tsx (3 hunks)
• packages/comments/src/browser/comments.service.ts (1 hunks)
• packages/components/package.json (1 hunks)
• packages/connection/package.json (1 hunks)
• packages/core-browser/package.json (1 hunks)
• packages/core-common/package.json (1 hunks)
• packages/core-electron-main/package.json (1 hunks)
• packages/core-node/package.json (1 hunks)
• packages/debug/package.json (1 hunks)
• packages/decoration/package.json (1 hunks)
• packages/design/package.json (1 hunks)
• packages/editor/package.json (1 hunks)
• packages/electron-basic/package.json (1 hunks)
• packages/explorer/package.json (1 hunks)
• packages/express-file-server/package.json (1 hunks)
• packages/extension-manager/package.json (1 hunks)
• packages/extension-storage/package.json (1 hunks)
• packages/extension/package.json (1 hunks)
• packages/file-scheme/package.json (1 hunks)
• packages/file-search/package.json (1 hunks)
• packages/file-service/package.json (1 hunks)
• packages/file-tree-next/package.json (1 hunks)
• packages/i18n/package.json (1 hunks)
• packages/keymaps/package.json (1 hunks)
• packages/logs-core/package.json (1 hunks)
• packages/main-layout/package.json (1 hunks)
• packages/markdown/package.json (1 hunks)
• packages/markers/package.json (1 hunks)
• packages/menu-bar/package.json (1 hunks)
• packages/monaco-enhance/package.json (1 hunks)
• packages/monaco/package.json (1 hunks)
• packages/notebook/package.json (1 hunks)
• packages/opened-editor/package.json (1 hunks)
• packages/outline/package.json (1 hunks)
• packages/output/package.json (1 hunks)
• packages/overlay/package.json (1 hunks)
• packages/preferences/package.json (1 hunks)
• packages/process/package.json (1 hunks)
• packages/quick-open/package.json (1 hunks)
• packages/remote-opener/package.json (1 hunks)
• packages/scm/package.json (1 hunks)
• packages/search/package.json (1 hunks)
• packages/startup/package.json (1 hunks)
• packages/static-resource/package.json (1 hunks)
• packages/status-bar/package.json (1 hunks)
• packages/storage/package.json (1 hunks)
• packages/task/package.json (1 hunks)
• packages/terminal-next/package.json (1 hunks)
• packages/testing/package.json (1 hunks)
• packages/theme/package.json (1 hunks)
• packages/toolbar/package.json (1 hunks)
• packages/types/manifest.json (1 hunks)
• packages/types/package.json (1 hunks)
• packages/utils/package.json (1 hunks)
• packages/variable/package.json (1 hunks)
• packages/webview/package.json (1 hunks)
• packages/workspace-edit/package.json (1 hunks)
• packages/workspace/package.json (1 hunks)
• tools/cli-engine/package.json (1 hunks)
• tools/dev-tool/package.json (1 hunks)
• tools/playwright/package.json (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

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.