chore(release): v0.21.14 - #9594
Conversation
qwen-code-dev-bot
left a comment
There was a problem hiding this comment.
Automated approval for the release version bump.
qwen-code-ci-bot
left a comment
There was a problem hiding this comment.
Automated second approval for the release version bump.
🖼️ 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 |
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. |
|
Automated release PR — version bumps and CHANGELOG for v0.21.14, syncing the release branch back into Template: the PR body is a single line rather than the full template, which is 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 v0.21.1–v0.21.13. Size: 688 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.14 的版本号同步和 CHANGELOG 更新,在 tag 切出后将发布分支同步回 模板:PR 正文只有一行,而非完整模板,这对机器人创建的发布 PR 来说是正常的。标题和正文已清楚说明目的。✓ 问题:不适用 —— 这是常规发布操作,不是 bug 修复或功能添加。发布工作流生成此 PR 以将版本元数据和变更日志同步回 方向:对齐 —— 发布 PR 是项目基础设施的核心部分,且与 v0.21.1–v0.21.13 的模式一致。 规模:23 个文件,+688/-61。全部改动均为 package.json 版本号、package-lock.json 版本同步或 CHANGELOG 内容 —— 未触及生产源代码,核心模块门控不适用。(标题为 方案:最小且聚焦 —— 正是发布 PR 应有的样子。lockfile 差异是对称的纯版本字符串替换(未新增、删除或调整依赖), 风险:无升级风险信号 —— 变更文件均未命中高风险路径。 进入代码审查 🔍 — Qwen Code · qwen3.8-max Reviewed at |
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,失败项排在最前。 One wrinkle worth naming: the branch head moved once mid-review (the release automation merged Not verified: nothing user-visible was driven live — there is nothing user-visible to drive; this diff is version metadata only. 中文说明代码审查先说独立方案:发布回同步应当只包含三类改动 —— 每个工作区 manifest 的 对照差异:
未触及任何正确性面(无生产源代码改动),无 AGENTS.md 规范问题,无阻塞项。 测试证据 —— 该提交自身的 CI,通过 API 读取(triage 从不执行 PR 代码)CI 表格见上方标记区域(finalize 任务会在 CI 结束后原地更新)。需要说明的一点:审查过程中分支头移动过一次(发布自动化合并了 未验证:未驱动任何用户可见行为 —— 本 diff 仅为版本元数据,没有可驱动的用户可见面。 — Qwen Code · qwen3.8-max Reviewed at |
|
Confidence: 5/5 — routine release sync; the diff is byte-for-byte release metadata, the tags and published releases all reconcile, and there is nothing in it that could behave differently than promised. Stepping back: this is the release workflow closing its loop for v0.21.14 — and, since Verdict: approve. One procedural note instead of an approval action: this bot's identity ( If the branch moves again before merge, the standing approvals dismiss and the release pipeline re-approves the new head — a re-run of 中文说明置信度:5/5 —— 常规发布回同步;diff 逐字节均为发布元数据,tag 与已发布的 release 全部吻合,其中不存在任何可能产生与承诺不同行为的内容。 整体来看:这是发布工作流为 v0.21.14 收尾 —— 由于 结论:approve。用一条流程说明代替实际的批准操作:本机器人身份( 若分支在合并前再次移动,已生效的批准将被驳回,发布流水线会在新 head 上重新批准 —— 届时重新运行 — Qwen Code · qwen3.8-max Reviewed at |
|
Released in v0.21.15. |
Automated release PR for v0.21.14. Syncs package.json versions and CHANGELOG.md on main.