From 19ed2733e338f3ce5c05d52dac1dba1fec5be678 Mon Sep 17 00:00:00 2001 From: hive-release-bot Date: Mon, 9 Nov 2026 16:00:06 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=96=20release:=20v6.5.3?= 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 v6.5.3 entry. See src/docs/releases.md. Signed-off-by: hive-release-bot --- CHANGELOG.md | 7 +++++++ changelog.d/fixed-fix-pr-any-hub.md | 1 - changelog.d/fixed-fork-guard-first-head.md | 1 - 3 files changed, 7 insertions(+), 2 deletions(-) delete mode 100644 changelog.d/fixed-fix-pr-any-hub.md delete mode 100644 changelog.d/fixed-fork-guard-first-head.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 7c6953706e..f21eca96df 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,13 @@ Hive did not historically maintain a complete changelog. This file starts a prag ## Unreleased +## 2026-11-09 (v6.5.3) + +### Fixed + +- A relay subscribed to several hives no longer refuses a `fix-pr` task for its contributor's own PR because it was polling another hive. On projectbluefin/utah-packages#972 (2026-11-09) the relay accepted a fix at 14:42:58Z, deferred it behind a headless task, and refused it with `Hub is not the active polling slot` the moment that task ended at 14:45:39Z; the hub booked a failed attempt and a five-minute retry. The relay now takes a `fix-pr` from any subscribed hub, makes that hub its active one and tells the other hives it is busy elsewhere, and the hub puts a fix refused for the polling slot back in its queue without counting an attempt. Ordinary work from a hive the relay is not polling is still refused. +- A fork PR whose only red check is a maintainer-run fork guard (such as a fork-gated Canary) is parked for a maintainer at `stage/085-needs-decision` on its first red head, instead of being sent back to its author first. On projectbluefin/utah-packages#972 (2026-11-09) the PR was opened from a fork at 14:41:50Z, its Canary refused it at 14:42:24Z with "This is expected, not something the author can fix", and at 14:45:32Z the hive nudged the author with `required-check-failing:Canary` and queued relay rework, because neither the fork-guard index (not yet read for that head) nor the stage record (never parked on a guard) knew about it; the PR reached 085 only at 14:50:57Z. The stage pass now reads such a head's own check annotations once, with the index's rule, and records the guard for later heads. A fork head with any other red check still goes to its author. + ## 2026-11-09 (v6.5.2) ### Fixed diff --git a/changelog.d/fixed-fix-pr-any-hub.md b/changelog.d/fixed-fix-pr-any-hub.md deleted file mode 100644 index c15eaf73c9..0000000000 --- a/changelog.d/fixed-fix-pr-any-hub.md +++ /dev/null @@ -1 +0,0 @@ -- A relay subscribed to several hives no longer refuses a `fix-pr` task for its contributor's own PR because it was polling another hive. On projectbluefin/utah-packages#972 (2026-11-09) the relay accepted a fix at 14:42:58Z, deferred it behind a headless task, and refused it with `Hub is not the active polling slot` the moment that task ended at 14:45:39Z; the hub booked a failed attempt and a five-minute retry. The relay now takes a `fix-pr` from any subscribed hub, makes that hub its active one and tells the other hives it is busy elsewhere, and the hub puts a fix refused for the polling slot back in its queue without counting an attempt. Ordinary work from a hive the relay is not polling is still refused. diff --git a/changelog.d/fixed-fork-guard-first-head.md b/changelog.d/fixed-fork-guard-first-head.md deleted file mode 100644 index 1954f14018..0000000000 --- a/changelog.d/fixed-fork-guard-first-head.md +++ /dev/null @@ -1 +0,0 @@ -- A fork PR whose only red check is a maintainer-run fork guard (such as a fork-gated Canary) is parked for a maintainer at `stage/085-needs-decision` on its first red head, instead of being sent back to its author first. On projectbluefin/utah-packages#972 (2026-11-09) the PR was opened from a fork at 14:41:50Z, its Canary refused it at 14:42:24Z with "This is expected, not something the author can fix", and at 14:45:32Z the hive nudged the author with `required-check-failing:Canary` and queued relay rework, because neither the fork-guard index (not yet read for that head) nor the stage record (never parked on a guard) knew about it; the PR reached 085 only at 14:50:57Z. The stage pass now reads such a head's own check annotations once, with the index's rule, and records the guard for later heads. A fork head with any other red check still goes to its author.