Repository navigation
docs(release): record verified 1.4.0 delivery - #6384
Conversation
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
loopx-agent
left a comment
There was a problem hiding this comment.
Reviewer: model_agent; model=gpt-6.1-sol; provider=OpenAI; runtime_reported; reasoning_effort=xhigh
Approval conclusion (author-owned PR; GitHub blocks formal self-approval)
精确 head c0f75640835f5fe54b18e276c88a6d601df0d358。
动机
从 release 手册判断可安装版本和验证边界的维护者与贡献者。公开 1.4.0 的各个制品已经交付,手册的历史记录却仍停留在 1.3.1,读者无法从这个既有入口核对本次冻结源码、安装结果与未认证边界。在原历史账本记录 1.4.0 的同一冻结提交、真实公开制品与升级回读,链接正式指南并明确保留失败及未测边界。只补充一条发布事实记录,不改晋升政策、测试门槛、产品默认、UI 或冻结 tag。
改动思路
复用原 release-readiness 的 named release 历史记录,遵守原“tag、release note、stable、update path 与 canary 一致后才添加”的要求。事实来自公开制品和实际安装回读,不从 GitHub 工作流成功状态推导安装完成。未来简化检查后保留一条完整记录,不新增账本、自动晋升或兼容层。
具体改动
docs/product/release-readiness.md:768 起仅新增1.4.0记录:准确公开时间、冻结1b452提交、新Goal的SQLite/硬租约与旧Goal审阅迁移边界、双语十五项使用指南、社区署名,以及包/桌面/更新/stable和正式个人图文指南链接。独立核对实际PyPI升级、1575打包源文件、3592桌面runtime源文件、哈希与托管来源、四种安装器、macOS签名/DMG/updater及stable激活。515公开smoke与360相关Python检查明确区别于全树扫描;DS22×2/六对照零失败的替代资格与此前Doubao失败分开记录。Windows执行、notarization、认证Host、外部后端和SQLite持续资格均不宣布通过。
规范基准为 dfbf8fa657b785f040723c0597c13c283476e666 的 docs/product/release-readiness.md:verified named release entry 行由实际 tag、notes、stable、updater 和 canary 一致性证明;preserve qualification limits 行由失败记录保留、focused/full 分界和明确未认证列表证明。
对主干的风险
这是公开文档历史记录;原晋升政策、兼容检查、已有版本、UI和tag均未变。最强反例是文档测试绿但制品不存在或来自另一个commit:真实公开文件、来源证明和隔离安装回读已独立排除,冻结后6244/6248未计入1.4.0。release-readiness、version-contract和artifacts三项smoke、公开边界零错误/警告、diff检查、精确质量回执及十五项最终远端使用校验通过。这是与文档事实风险对应的验证集,不重跑无关Todo/lease运行检查;没有CI查询或新的运行时全树通过声称。个人标识、密钥、私有日志与设备路径未进入diff。
我的整体评价
APPROVE,goal_achieved针对本条发布记录。原有owner和历史入口足够,范围小但覆盖完整交付事实和限制,没有新分类、默认开关、agent决策文字、领域义务或权限。只补充一条发布事实记录,不改晋升政策、测试门槛、产品默认、UI 或冻结 tag。飞书指南仍采用既有分享范围,对外链接只读范围须由维护者另行明确选择。已有授权支持精确head公开评审、readiness后admin merge;绿检查与此结论本身不授予合并权。
English verdict: APPROVE at c0f75640835f5fe54b18e276c88a6d601df0d358. One existing release-history entry records independently verified1.4.0 public delivery and explicit qualification limits. Three focused release smokes, public-boundary/diff checks, exact-scope quality and actual package/desktop/updater/stable/guide readbacks pass. No runtime, promotion policy, first-screen UI or immutable tag changes; external guide sharing scope remains separately pending.
The release readiness ledger still ends at 1.3.1 after v1.4.0 package, desktop, updater and stable delivery. Record the verified frozen release source, operating-guide links and actual public artifact/install readbacks in the existing historical ledger. Preserve the distinction between final-source focused checks and a complete Python sweep, retain prior Doubao failures, and keep unqualified platform/backend/sustained SQLite limits explicit.
Validation: release-readiness documentation, version contract and artifact smokes; public-boundary and diff checks; real public PyPI upgrade from 1.3.1, package/source hash equality and hosted attestations, all four desktop checksums/attestations, macOS bundle and updater signature/runtime checks, stable source/runtime activation, personal guide ownership/released images/native rendering, and all 15 bilingual operating entries before/after remote release readback. This documentation-only record changes no promotion or validation policy, runtime, first-screen UI or tag. Existing contributor sections remain identical between the release preparation PR and published bilingual body.
The future-facing pass keeps this fact in the existing release ledger; no parallel report, state owner or release mechanism is needed.