| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-09-11 | 3.4 kB | |
| v0.4.6 source code.tar.gz | 2026-09-11 | 894.5 kB | |
| v0.4.6 source code.zip | 2026-09-11 | 1.0 MB | |
| Totals: 3 Items | 1.9 MB | 0 | |
v0.4.6
Changelog
Features
- 技术债:把发布子系统(17 个函数 / 1018 行)从 runner.py 移入 release.py (Issue [#286]; PR [#696])
- 部署基准可配置:core 运行前不再无条件追 origin/main,支持 update_channel(分支 / 最新 release / 钉 tag/commit) (Issue [#534])
- Bug: check_release_gates 对刚 push 的 release 提交空 check-runs 判定 nothing to gate——CI 注册滞后窗口内带病提交过门(假成功) (Issue [#657]; PR [#670])
Reliability and recovery
- Bug: 双实例认领同一 Issue 的 TOCTOU——复查走搜索索引(最终一致)形同虚设,败者把在途交付打成 ai-blocked (Issue [#658]; PR [#668])
Deployment and operations
- ops 票需要完整执行能力(部署/写 GitHub/任意平台 CLI):复用完整执行代理 + ops 剧本,废弃白名单沙箱方案 (Issue [#537]; PR [#703])
- P0:示例配置本身跑不起来——.orbi.example.toml 的两个 source_repos 被 runner 拒绝,而 cli 不校验导致 doctor 全绿 (Issue [#697]; PR [#700])
Bug fixes
- runner_health 崩溃计数把正常退出/预检失败计入,健康部署常驻 crash_loop 误报并派发幻影 ai-ready 任务;一次真实崩溃双行计数使阈值折半 (Issue [#617]; PR [#619])
- P0:429 重试计数随进程重启归零,limit=5 永不生效——交付无限循环、永不转 ai-fix-needed (Issue [#698]; PR [#701])
-
CI failure: tests on branch fix/claim-race-yield (pull_request) (Issue [#704])
-
tag:
v0.4.6 - release commit:
000ceee47fab50549b6d83e9f66085d396f9a06d - release task: Issue [#706]
Scope (verified item by item)
- Issue [#704] closed
- Issue [#702] closed (not planned — duplicate of [#658], excluded from this release)
- Issue [#698] closed
- Issue [#697] closed
- Issue [#658] closed
- Issue [#657] closed
- Issue [#617] closed
- Issue [#537] closed
- Issue [#534] closed
- Issue [#286] closed
Pre-release gates
- no open Issue in milestone 'v0.4.6' carries ai-in-progress / ai-pr-opened / ai-fix-needed
- CI on the release commit: 1 check(s) all success/neutral/skipped
Tests
- release tests gated by GitHub Actions CI on the release commit [000cee] (the [#268] CI-wait gate; no local test execution)
run_id=27888bbd
Correction (post-release): an earlier version of these notes listed Issue [#702] with PR [#705] under "Reliability and recovery". That entry was wrong: [#702] was closed as NOT_PLANNED (a duplicate of [#658]) and PR [#705] has never been merged. The concurrent-claim race is fixed in this release by #658 / PR [#668] only. Tracked as [#707].