docs(release): record verified 1.2.2 publication and preflight - #5233
Conversation
Signed-off-by: huangruiteng <14976749+huangruiteng@users.noreply.github.com>
huangruiteng
left a comment
There was a problem hiding this comment.
Approval conclusion (author-owned PR; GitHub blocks formal self-approval)
Reviewed exact head 5233@123807a1af6a3b3f6d919ed25f5a1258f0a955a4. No blocking finding.
动机
1.2.2 已实际发布,但现有发布指南仍停在 1.2.1,当前安装与构建证明命令还使用旧仓库命名空间。此改动把已完成的公开发行结果写回既有入口,并补齐冻结源码前可重复执行的文档预检,减少以后再次发现版本、帮助和书籍漂移的维护成本。
改动思路
复用现有 Named Version Contract、Public Release Timeline 和三个验证器。构建发布仍由原工作流负责,stable 仍由维护者在资格通过后推进;文档只记录真实结果,不增加权限、机器门禁或平行状态。最强反例是文字 smoke 通过但产物尚未发布,因此这里核对了实际公开工件与源码,再接受时间线记录。
具体改动
关键内容讲解
唯一文件是 docs/product/release-readiness.md,增加 26 行、删除 4 行。四处当前获取与证明命令改为正式组织仓库,历史示例保留;新增帮助目录、版本化 manpage、开发者书籍的已有预检命令。新增 1.2.2 的真实发布时间、源码和包、四个桌面工件、签名更新、PyPI 安装、Pages、stable 读回结果,并公开保留首次 fixture 清理失败、同源全量重跑通过以及尚未证明消除的清理竞态,关联现有生命周期 owner。
对主干的风险
主要风险是用文本检查替代真实发布证明,或者把一次重跑描述为竞态已解决。该发行已经独立下载验证十一项资产、包与桌面构建证明、更新签名,并通过全新 PyPI 运行和公开网站读回;源码与 stable 一致。三个既有文档/帮助/书籍 smoke、空白、公开边界和精确质量检查通过,原生选中的 17 项检查全部通过,无直接失败、跳过或人工 hold。公开边界干净;两项本地注册表告警与此文件无关。PR CI 按配置不查询或等待。没有运行时、类型状态、默认启用、权限、通用义务、首屏或自动载入指令变化;无需新增前端/Lark 配套。
我的整体评价
批准当前精确 head。此文档闭环已完成;持续发布准备和读者验证路径均改善,发行内容与升级行为不变。未来改进检查已应用为复用既有 owner 和验证器,未新增测试或抽象。残余 fixture 清理风险如实保留,本 PR 不声称修复;整版发行的七个成功验证/发布工作流和实际公共读回已完成。
English verdict: APPROVE - Exact head 123807a; factual 1.2.2 release closeout, three documentation smokes and all 17 selected native checks pass; public artifacts/stable independently verified; existing cleanup-race limit retained.
The public release guide still ends at 1.2.1 and uses the former repository namespace for current acquisition/provenance commands. Record the published 1.2.2 source and verified package, four desktop artifacts, signed updates, PyPI runtime, Pages and stable promotion; correct those four current references.
Reuse the existing help/manpage/book preflight before source freeze. Preserve the first full-public fixture-cleanup failure and successful complete same-source rerun under unchanged budgets, with the existing lifecycle owner link.
Validation: release-readiness, CLI help/manpage and developer-book smokes pass; generated manpage remains unchanged; whitespace and the changed-document public-boundary scan pass. Independent public readback and all seven selected qualification/publication workflows pass at the tagged source. The future-facing pass reuses the existing guide and validators; no runtime, new test or permission change.