chore(release): v0.21.15 - #9606
Closed
qwen-code-review-bot wants to merge 2 commits into
Closed
Conversation
qwen-code-review-bot
requested review from
tanzhenxin,
wenshao and
yiliang114
as code owners
August 20, 2026 18:04
qwen-code-review-bot
requested review from
LaZzyMan and
doudouOUC
as code owners
August 20, 2026 18:04
qwen-code-dev-bot
approved these changes
Aug 20, 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 20, 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 20, 2026 18:04
Collaborator
|
✅ Qwen Triage finished — CI landed green on ✅ Qwen Triage 已完成 —— |
Collaborator
|
Automated release PR — version bumps and CHANGELOG for v0.21.15, syncing the release branch back into Template: the PR body is a single line rather than the full template — expected for bot-created release PRs; the purpose is self-evident from the title and body. ✓ Problem: N/A — this is a routine release chore, not a bug fix or feature. The release workflow generates it to sync version metadata and the changelog back to Direction: aligned — release PRs are core project infrastructure, and this follows the same shape as the previous releases (v0.21.14's PR touched the identical 23-file set). Size: 394 additions / 61 deletions across 23 files. Every change is a Approach: minimal and focused — exactly what a release PR should be. The lockfile diff is a symmetric swap of pure version strings (no dependency added, removed, or re-ranged), the Risk: no elevated risk signals — none of the changed files match high-risk paths. Moving on to code review. 🔍 中文说明自动化发布 PR —— v0.21.15 的版本号同步和 CHANGELOG 更新，在 tag 切出后将发布分支同步回 模板：PR 正文只有一行而非完整模板 —— 这对机器人创建的发布 PR 来说是正常的，标题和正文已清楚说明目的。✓ 问题：不适用 —— 这是常规发布操作，不是 bug 修复或功能添加。发布工作流生成此 PR 以将版本元数据和变更日志同步回 方向：对齐 —— 发布 PR 是项目核心基础设施，且与此前发布的形态一致（v0.21.14 的 PR 触及完全相同的 23 个文件集合）。 规模：23 个文件，+394/-61。全部改动均为 package.json 版本号、package-lock.json 版本同步或 CHANGELOG 内容 —— 未触及生产源代码，核心模块门控不适用。标题为 方案：最小且聚焦 —— 正是发布 PR 应有的样子。lockfile 差异为对称的纯版本字符串替换（未新增、删除或调整任何依赖）， 风险：无升级风险信号 —— 变更文件均未命中高风险路径。 进入代码审查 🔍 — Qwen Code · qwen3.8-max Reviewed at |
Collaborator
Code reviewIndependent proposal first: a release sync-back should contain exactly three kinds of edits — a Reading the diff against that baseline:
No correctness surface is touched (no production source changes), no AGENTS.md convention issues, nothing blocking. Test evidence — this commit's own CI, read via the API (PR code is never executed in triage)Final CI results for
One row per check name (latest run); skipped checks omitted; failures sort first. / 每个检查名一行（取最新一次运行），省略 skipped，失败项排在最前。 Snapshot at review time, not a final result: the main Not verified: nothing user-visible was driven live — there is nothing user-visible to drive; this diff is version metadata only, so no sandboxed verification lane applies either. 中文说明代码审查先说独立方案：发布回同步应当只包含三类改动 —— 每个发布序列 manifest 的 对照差异：
未触及任何正确性面（无生产源代码改动），无 AGENTS.md 规范问题，无阻塞项。 测试证据 —— 该提交自身的 CI，通过 API 读取（triage 从不执行 PR 代码）CI 表格见上方标记区域（finalize 任务会在 CI 结束后原地更新）。审查时点为快照而非最终结果：主 未验证：未驱动任何用户可见行为 —— 本 diff 仅为版本元数据，没有可驱动的用户可见面，因此也无需沙箱验证通道。 — Qwen Code · qwen3.8-max Reviewed at |
Collaborator
|
Confidence: 5/5 — routine release sync; the diff is byte-for-byte release metadata, and everything the release claims checks out independently. This is the clean end of the gate's spectrum. The diff matches the independent proposal exactly — version bumps, lockfile sync, one changelog section, nothing else — and it is the same 23-file shape as the previous releases. I verified the claims rather than taking them on faith: the tag exists, the release was published before this PR opened, every manifest at Approval status: triage's own commit-pinned approval already stands on One note for the maintainer: branch protection still reports 中文说明置信度：5/5 —— 常规发布回同步；diff 逐字节均为发布元数据，且发布声明的每一项均已独立核实。 这是门控中最干净的一类。diff 与独立方案完全一致 —— 版本号升级、lockfile 同步、一个 changelog 段落，别无其他 —— 且与以往发布相同的 23 文件形态。我独立核实了各项声明而非直接采信：tag 存在，release 在本 PR 创建前已发布，main 上所有处于 审批状态：triage 自身的绑定提交的审批已存在于 给维护者的提示：尽管已有两个机器人审批，分支保护仍显示 — Qwen Code · qwen3.8-max Reviewed at |
Collaborator
🖼️ web-shell visual previewRendered against a mock daemon (no real backend): the PR base vs this PR head Screenshots · before / afterFull-resolution recordings (.webm) are attached to the workflow run. — Qwen Code · web-shell visuals |
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. |
qwen-code-ci-bot
approved these changes
Aug 20, 2026
qwen-code-ci-bot
left a comment
qwen-code-ci-bot
left a comment
Collaborator
There was a problem hiding this comment.
No issues found. LGTM! ✅
— qwen3.8-max via Qwen Code /review (v0.21.15)
wenshao
approved these changes
Aug 23, 2026
Collaborator
|
@qwen-code /resolve |
Collaborator
|
Qwen Code attempted to resolve merge conflicts but the run did not complete successfully. Check the workflow run for full logs. |
Collaborator
|
Closing as obsolete — everything this PR carries is already on
The 23 conflicting files (CHANGELOG.md, package-lock.json, 21 package.json) are all The |
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.21.15. Syncs package.json versions and CHANGELOG.md on main.