chore(release): v0.22.3 - #10424
Merged
Merged
Conversation
qwen-code-review-bot
requested review from
LaZzyMan,
doudouOUC,
tanzhenxin,
wenshao and
yiliang114
as code owners
August 28, 2026 17:43
qwen-code-dev-bot
approved these changes
Aug 28, 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 28, 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 28, 2026 17:43
Collaborator
wenshao
approved these changes
Aug 28, 2026
Collaborator
|
Gate check for the v0.22.3 release PR. This is the repo's own release automation — Problem: observed by construction — the v0.22.3 release was published at 17:16 UTC on 2026-08-28 with tag Direction: routine release operations, fully within scope. The version steps 0.22.2 → 0.22.3 with v0.22.2 shipped two days ago, so the CHANGELOG compare anchor is correctly Size: 244 changed lines (177+/67−) across 25 files, all release metadata (workspace manifests, lockfile, generated CHANGELOG). No Approach: minimal — exactly the two commits the automation produces: the bump Risk: no high-risk paths touched; no elevated risk signals. Moving on to code review. 🔍 中文说明v0.22.3 发布 PR 的门禁检查。 这是仓库自己的发布自动化—— 问题：由流程本身即可观测——v0.22.3 release 已于 2026-08-28 17:16 UTC 发布，tag 方向：例行发布操作，完全在职责范围内。版本从 0.22.2 升至 0.22.3，v0.22.2 两天前刚发布，因此 CHANGELOG 比较锚点正确地使用 规模：25 个文件共 244 行改动（177+/67−），全部为发布元数据（workspace manifest、lockfile、生成的 CHANGELOG）。未触及任何 方案：最小化——恰好是自动化产出的两个提交：版本升级提交 风险：未触及高风险路径，无升级风险信号。 进入代码审查。🔍 — Qwen Code · qwen3.8-max Reviewed at |
Collaborator
|
Code review — the diff matches the expected release-sync shape exactly, and each claim below was verified 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 full SDK Java matrix (all five legs), and both Desktop Shell builds were green. The Node unit suite (ubuntu), web-shell visuals capture, daemon E2E, and the no-AK integration lane were still in flight. The skipped checks are the off-Linux unit legs and CLI integration lane — the standing pattern for version-only release diffs (same as #10166, #9736) — plus 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 a 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 与 no-AK 集成测试仍在运行。跳过的检查是非 Linux 的单测与 CLI 集成分片——纯版本 diff 的既有处理方式（与 #10166、#9736 相同）——以及与内容无关的机器人编排任务重复分发。表格会在剩余检查完成后原地更新。 真实场景测试：不适用——版本元数据与生成的 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.3 release. 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 workspaces stay untouched, and the changelog matches the published notes entry for entry. The only thing in the diff that isn't self-evident is the mem0 workspace's 0.1.0 → 0.22.3 jump, and that is the automation doing its job on a workspace that landed between releases — the same pattern as Approval: none needed from this pass. The release flow's two automated approvals ( 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.3 release 对账一致。 退一步看：发布回同步不存在明显更优的落地方式，而本 PR 正是理想形态——版本升级提交即 tag 提交，changelog 同步提交即 PR head，lockfile 与每个 manifest 对称，独立版本管理的 workspace 未被触碰，changelog 与已发布的 release notes 逐条一致。diff 中唯一不那么自明的是 mem0 workspace 从 0.1.0 跳到 0.22.3，这是自动化在两次发布之间合入的 workspace 上做的正常对齐——与 v0.22.2 周期中 批准：本次审查无需发出。发布流程的两个自动化批准（ 六个月后维护这些内容不会有任何抱怨：生成的元数据、确定性的提交、零源代码改动。 — 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. |
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.3. Syncs package.json versions and CHANGELOG.md on main.