chore(release): v0.22.2 - #10166
Merged
Merged
Conversation
qwen-code-review-bot
requested review from
tanzhenxin and
wenshao
as code owners
August 26, 2026 13:34
qwen-code-review-bot
requested review from
LaZzyMan,
doudouOUC,
qqqys and
yiliang114
as code owners
August 26, 2026 13:34
qwen-code-dev-bot
approved these changes
Aug 26, 2026
qwen-code-dev-bot
left a comment
qwen-code-dev-bot
left a comment
Collaborator
There was a problem hiding this comment.
Automated approval for the release version bump.
qwen-code-ci-bot
approved these changes
Aug 26, 2026
qwen-code-ci-bot
left a comment
qwen-code-ci-bot
left a comment
Collaborator
There was a problem hiding this comment.
Automated second approval for the release version bump.
qwen-code-ci-bot
enabled auto-merge
August 26, 2026 13:34
Collaborator
yiliang114
approved these changes
Aug 26, 2026
Collaborator
|
Gate check for the v0.22.2 release PR. This is the repo's own release automation — Problem: observed by construction — the v0.22.2 release was published at 12:57 UTC with tag Direction: routine release operations, fully within scope. One thing worth knowing for anyone reading the numbers: the version steps 0.22.0 → 0.22.2 — v0.22.1 was cut but its sync-back PR #10025 closed unmerged and no v0.22.1 tag or release exists, so the CHANGELOG compare anchor is correctly Size: 394 changed lines across 24 files, all release metadata (workspace manifests, lockfile, generated CHANGELOG). No Approach: minimal — exactly the two commits the automation produces (the bump and the changelog sync), nothing extra riding along. Risk: no high-risk paths touched; no elevated review depth required. Moving on to code review. 🔍 中文说明v0.22.2 发布 PR 的门禁检查。 这是仓库自己的发布自动化—— 问题：由流程本身即可观测——v0.22.2 release 已于 12:57 UTC 发布，tag 方向：例行发布操作，完全在职责范围内。读版本号时需要知道一点：版本从 0.22.0 直接跳到 0.22.2——v0.22.1 曾切版但其回同步 PR #10025 关闭未合并，v0.22.1 不存在 tag 和 release，因此 CHANGELOG 的比较锚点正确地使用 规模：24 个文件共 394 行改动，全部为发布元数据（workspace manifest、lockfile、生成的 CHANGELOG）。未触及任何 方案：最小化——恰好是自动化产出的两个提交（版本升级 + changelog 同步），没有夹带任何其他改动。 风险：未触及高风险路径，无需升级审查深度。 进入代码审查。🔍 — Qwen Code · qwen3.8-max Reviewed at |
Collaborator
|
Code review — the diff matches the expected release-sync shape exactly, and I verified each claim against the repo state rather than the PR text:
Nothing for a human to second-guess here. Test evidence — the PR's own CI on the reviewed commit, fetched via API (triage never runs PR code). At review time: Security Checks (TruffleHog secret scan, dependency CVE audit), the SDK Java matrix, and the Desktop Shell builds were green. The Node unit suite (ubuntu), web-shell visuals capture, and the daemon E2E were still in flight when the release automation's auto-merge landed this PR at 13:39 UTC — the standing behaviour for version-only release diffs (same pattern as #9736), not a PR defect. The remaining skipped/cancelled checks are duplicate bot-orchestration dispatches, unrelated to the content. The table updates in place as the in-flight checks settle.
Real-scenario testing: N/A — version metadata and generated changelog carry no user-visible behaviour to drive. 中文说明代码审查 —— diff 与预期的发布回同步形态完全一致，以下每一点都是对照仓库实际状态核验的，而非采信 PR 正文：
没有需要人工二次确认的地方。 测试证据 —— 来自被审提交自身的 CI，通过 API 获取（审查流程从不运行 PR 代码）。审查时点：安全检查（TruffleHog 密钥扫描、依赖 CVE 审计）、SDK Java 矩阵与 Desktop Shell 构建均为绿。Node 单测（ubuntu）、web-shell 视觉截图与 daemon E2E 在 13:39 UTC 发布自动化 auto-merge 合并本 PR 时仍在运行——这是纯版本 diff 的既有处理方式（与 #9736 相同），不是 PR 缺陷。其余跳过/取消的检查是机器人编排任务的重复分发，与内容无关。表格会在剩余检查完成后原地更新。 真实场景测试：不适用——版本元数据与生成的 changelog 没有任何可操作的用户可见行为。 — Qwen Code · qwen3.8-max Reviewed at |
Collaborator
|
Confidence: 5/5 — routine release sync-back; the diff is pure release metadata and every piece reconciles with the published v0.22.2 release. ℹ️ This PR merged mid-triage (13:39 UTC, via the release automation's auto-merge after the two required bot approvals), so this comment is an audit record rather than a gate decision — triage issued no approval and none was needed: the release flow's own approvals already stood on this exact commit, and the merge landed before this pass finished. Stepping back: there is no meaningfully different way to land a release sync-back, and this one is exactly the shape one would choose — the bump commit is the tagged commit, the changelog sync is the head, the lockfile mirrors every manifest, independently versioned packages stay untouched, and the file set matches prior release PRs (#9594, #9736) modulo the new dws workspace joining this cycle. The v0.22.1 gap is explained by the repo state, not by anything in this diff. The only judgment call on record is the automation merging while the ubuntu unit suite, web-shell visuals, and daemon E2E were still running — standing behaviour for version-only release diffs, matching every prior release sync, and not something this review would have held the merge for. If I had to maintain this in six months there would be nothing to curse: generated metadata, deterministic commits, zero source changes. 中文说明置信度：5/5 —— 例行发布回同步；diff 全部为发布元数据，每一部分都与已发布的 v0.22.2 release 对账一致。 ℹ️ 本 PR 在审查进行中被合并（13:39 UTC，发布自动化在获得两个必需的机器人批准后经 auto-merge 合并），因此本条评论是审查存档而非门禁结论——审查流程未发出也无需发出批准：发布流程自身的批准已落在同一提交上，合并在本次审查完成前已经发生。 退一步看：发布回同步不存在明显更优的落地方式，而本 PR 正是理想形态——版本升级提交即 tag 提交，changelog 同步提交即 PR head，lockfile 与每个 manifest 对称，独立版本管理的包未被触碰，文件集与历次发布 PR（#9594、#9736）一致（本周期新增 dws workspace 除外）。0.22.1 的版本空档由仓库状态解释，与本 diff 无关。唯一值得记录的判断是自动化在 ubuntu 单测、web-shell 视觉截图与 daemon E2E 仍在运行时完成合并——这是纯版本 diff 回同步的既有行为，与历次发布一致，本次审查也不会为此拦截合并。 六个月后维护这些内容不会有任何抱怨：生成的元数据、确定性的提交、零源代码改动。 — Qwen Code · qwen3.8-max Reviewed at |
Contributor
Code Coverage Summary
CLI Package - Full Text ReportCore Package - Full Text ReportFor detailed HTML reports, please see the 'coverage-reports-22.x-ubuntu-latest' artifact from the main CI run. |
Collaborator
|
Released in v0.22.3. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated release PR for v0.22.2. Syncs package.json versions and CHANGELOG.md on main.