| v0.20.6 | 8/27/2026 | 80 | 0 | |
| v0.20.5 | 8/21/2026 | 95 | 0 | |
| v0.20.4 | 8/18/2026 | 89 | 0 | |
| v0.20.3 | 8/17/2026 | 80 | 0 | |
| v0.20.2 | 8/16/2026 | 83 | 0 | |
| v0.20.1 | 8/13/2026 | 86 | 0 | |
| v0.20.0 | 8/8/2026 | 95 | 0 | |
| v0.19.1 | 7/30/2026 | 95 | 0 | |
| v0.19.0 | 7/20/2026 | -283 | 90 | v0.19.0 keeps collecting sharp edges: packaging gaps, state DB corruption, updater deadlocks, provider routing detours. The deploy room is now mostly coffee and incident notes. |
| v0.18.2 | 7/8/2026 | -259 | 95 | v0.18.2 was already carrying a heavy pack; fresh backfill found more gateway/channel baggage, not a clean bill of health. |
| v0.18.1 | 7/8/2026 | 66 | 5 | v0.18.1 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.18.0 | 7/1/2026 | -244 | 88 | v0.18.0 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.17.0 | 6/19/2026 | -237 | 93 | v0.17.0 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.16.0 | 6/6/2026 | -336 | 142 | v0.16.0 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.15.2 | 5/29/2026 | 23 | 33 | v0.15.2 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.15.1 | 5/29/2026 | 32 | 19 | v0.15.1 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.15.0 | 5/28/2026 | -91 | 28 | v0.15.0 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.14.0 | 5/25/2026 | 52 | 11 | v0.14.0 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.13.0 | 5/7/2026 | 39 | 17 | v0.13.0 also inherits the packaged-test kill-switch problem: the safety net stayed home while the canary brought a chainsaw. |
| v0.12.0 | 4/30/2026 | 63 | 12 | v0.12.0 looked tidy from a distance; config and provider evidence now says the closet was doing the hiding. |
| v0.11.0 | 4/23/2026 | 65 | 12 | v0.11.0 earns more dents: Python 3.9 import crash, email fetch failure, and a mid-tool stream stall. Classic “works until demo time” energy. |
| v0.10.0 | 4/16/2026 | 65 | 12 | v0.10.0 picks up more gateway and plugin bruises; Discord also decided silence should be delivered loudly. |
| v0.9.0 | 4/13/2026 | 63 | 8 | v0.9.0 improves the line but still has sharp edges in dashboard/gateway connectivity, custom-provider paths, memory prefetch, Feishu approvals, and OpenRouter. |
| v0.8.0 | 4/8/2026 | 66 | 10 | v0.8.0 is provider-routing noisy: MiniMax/OpenRouter failures, tool-call instability, Discord limits, Windows startup crashes, and local-model retry loops. |
| v0.7.0 | 4/3/2026 | 60 | 13 | v0.7.0 has broad gateway and memory regressions: command routing, provider Unicode failures, service lifetime, and profile/session isolation. |
| v0.6.0 | 3/30/2026 | 72 | 7 | Early API/gateway rough edges: Telegram model control, fallback config, profile isolation, and one-time approvals all have explicit 0.6.0 repros. |
| v0.5.0 | 3/28/2026 | 60 | 9 | Fewer defensible rows than v0.4.0, but UI command dispatch, Matrix/Discord delivery, MCP args, provider streaming, and Telegram group behavior pass the gate. |
| v0.4.0 | 3/24/2026 | 29 | 18 | A noisy release: packaging, update, provider routing, gateway, Matrix/MCP, cron, and config overwrite evidence all pass the version gate. |
| v0.3.0 | 3/17/2026 | 61 | 11 | Provider routing, gateway connectors, browser control, Docker buildability, and runtime hangs are all represented. |
| v0.2.0 | 3/12/2026 | 56 | 11 | Early release shows provider/tool discovery, gateway safety, and delivery-loop failures in live reports. |