| v2026.5.7 | 5/7/2026 | 62 | 7 | v2026.5.7 is a regression fiesta. Upgrade to 2026.5.6 or wait for 2026.5.8. |
| v2026.5.6 | 5/6/2026 | 60 | 5 | Gateway watchdog in death spiral, sessions broken, plugin migrations failing. **Stay on v2026.5.5 ASAP.** |
| v2026.5.5 | 5/6/2026 | 68 | 4 | Stay on v2026.4.23. v2026.5.5 brings breaking command routing, approval security bypass, and context overflow issues. Rollback recommended. |
| v2026.5.4 | 5/5/2026 | 65 | 12 | "Someone shipped a grenade and forgot to pull the pin. 19 different subsystems on fire." |
| v2026.5.3-1 | 5/4/2026 | 23 | 24 | Evidence backfill changed the verdict: v2026.5.3-1 shipped with packaging breakage plus channel/runtime regressions across Docker, Discord, WhatsApp, iMessage, Telegram, Matrix, Feishu, Browser, memory, and agent runtimes. Skip it. |
| v2026.5.3 | 5/4/2026 | 74 | 5 | Five unpatched regressions in critical paths. Gateway stability is actively getting worse. **Stay on v2026.5.2** or wait for v2026.5.4 patch. |
| v2026.5.2 | 5/3/2026 | 44 | 14 | Not a ghost town โ just an under-scanned release. v2026.5.2 had gateway, compaction, upgrade, and plugin-path regressions hiding in plain sight. |
| v2026.4.29 | 4/30/2026 | 58 | 10 | Six hours after release, the bug tracker looks like a 3am incident channel. Hard pass. |
| v2026.4.27 | 4/29/2026 | 64 | 10 | "Works on my machine" โ except your machine, where the gateway is on fire. |
| v2026.4.26 | 4/28/2026 | 36 | 14 | This one's a roach motel โ your gateway checks in, but it never checks out. Skip it. Wait for 2026.4.27+. |
| v2026.4.25 | 4/27/2026 | 67 | 5 | Evidence says this one deserves caution. |
| v2026.4.24 | 4/25/2026 | 74 | 4 | Evidence says this one deserves caution. |
| v2026.4.23 | 4/24/2026 | 82 | 0 | No major evidence yet. The release gets to keep its shoes on. |