From 27c76174ef5c2bf9105b191aaf6b0f7567365fd7 Mon Sep 17 00:00:00 2001 From: hive-release-bot Date: Mon, 9 Nov 2026 19:28:39 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=96=20release:=20v5.209.7?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Automated release commit. Compiles changelog.d/ fragments and moves the CHANGELOG.md Unreleased section into a dated v5.209.7 entry. See src/docs/releases.md. Signed-off-by: hive-release-bot --- CHANGELOG.md | 6 ++++++ changelog.d/fixed-17410-cmdlog-next-seq-pin.md | 1 - 2 files changed, 6 insertions(+), 1 deletion(-) delete mode 100644 changelog.d/fixed-17410-cmdlog-next-seq-pin.md diff --git a/CHANGELOG.md b/CHANGELOG.md index a4f9de14a9..7fefad538a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,12 @@ Hive did not historically maintain a complete changelog. This file starts a prag ## Unreleased +## 2026-11-09 (v5.209.7) + +### Fixed + +- Crux's command log (`GET /v1/runs/{id}/cmdlog`) no longer pins a follower's `next_seq` forever ([#17410](https://github.com/hivecommons/hive/issues/17410)). A command that ended `unfinished` (the launcher failed without an exit the runtime could read) is now terminal, so `next_seq` moves past it; a command left in flight by a runner that died is ended `unfinished` when its log is next opened, which `crux serve` now does for every run it reconciles at start; and `more` is never true on a page whose `next_seq` did not move, so a "page while `more`" loop such as `crux cmdlog list --all` can no longer spin on the same request. + ## 2026-11-09 (v5.209.6) ### Fixed diff --git a/changelog.d/fixed-17410-cmdlog-next-seq-pin.md b/changelog.d/fixed-17410-cmdlog-next-seq-pin.md deleted file mode 100644 index a60d09dd0d..0000000000 --- a/changelog.d/fixed-17410-cmdlog-next-seq-pin.md +++ /dev/null @@ -1 +0,0 @@ -- Crux's command log (`GET /v1/runs/{id}/cmdlog`) no longer pins a follower's `next_seq` forever ([#17410](https://github.com/hivecommons/hive/issues/17410)). A command that ended `unfinished` (the launcher failed without an exit the runtime could read) is now terminal, so `next_seq` moves past it; a command left in flight by a runner that died is ended `unfinished` when its log is next opened, which `crux serve` now does for every run it reconciles at start; and `more` is never true on a page whose `next_seq` did not move, so a "page while `more`" loop such as `crux cmdlog list --all` can no longer spin on the same request.