From d405c95641ce2a8775d70b689dda2741efee2f2e Mon Sep 17 00:00:00 2001 From: hive-release-bot Date: Sun, 8 Nov 2026 18:50:35 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=96=20release:=20v5.203.0?= 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.203.0 entry. See src/docs/releases.md. Signed-off-by: hive-release-bot --- CHANGELOG.md | 7 +++++++ changelog.d/added-crux-s1-s2-followups.md | 1 - changelog.d/added-maintainer-notes.md | 1 - 3 files changed, 7 insertions(+), 2 deletions(-) delete mode 100644 changelog.d/added-crux-s1-s2-followups.md delete mode 100644 changelog.d/added-maintainer-notes.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 42c718eda3..909dee63dc 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-08 (v5.203.0) + +### Added + +- crux: checkout requests are bounded by a server ceiling (`--checkout-max-bytes`, `CRUX_CHECKOUT_MAX_BYTES`), private repositories clone with `CRUX_CHECKOUT_TOKEN` through a credential helper that never logs the token, and the `job` run backend isolates each Job with a deny-all NetworkPolicy by default (`job_network: none|host|default`) +- **Maintainer notes on the Activity Monitor.** With more than one maintainer running a hive, there was nowhere on the dashboard to leave a colleague a word about an item short of a GitHub comment everyone else could read. Each row now carries a 🗒 button with a count badge: click it for the item's maintainer notes — who wrote what, when — and a one-line composer (⌘/Ctrl+Enter). Notes are stored on the spoke in the append-only `/data/maintainer-notes.jsonl` and are never written to GitHub; every signed-in maintainer sees them, adding one takes write on the repo, deleting is author-or-owner, and the `maintainer-notes` SSE frame keeps the other browsers live. The scheduler types an item's notes into the agent's kick under `# Maintainer notes` (1 KB cap), so what a maintainer wrote on the row reaches whoever picks it up. `GET`/`POST /api/notes`, `DELETE /api/notes/{id}`; audited as `maintainer_note_add` / `maintainer_note_delete`. + ## 2026-11-08 (v5.202.0) ### Added diff --git a/changelog.d/added-crux-s1-s2-followups.md b/changelog.d/added-crux-s1-s2-followups.md deleted file mode 100644 index 58bc37f5a6..0000000000 --- a/changelog.d/added-crux-s1-s2-followups.md +++ /dev/null @@ -1 +0,0 @@ -- crux: checkout requests are bounded by a server ceiling (`--checkout-max-bytes`, `CRUX_CHECKOUT_MAX_BYTES`), private repositories clone with `CRUX_CHECKOUT_TOKEN` through a credential helper that never logs the token, and the `job` run backend isolates each Job with a deny-all NetworkPolicy by default (`job_network: none|host|default`) diff --git a/changelog.d/added-maintainer-notes.md b/changelog.d/added-maintainer-notes.md deleted file mode 100644 index 9949131cd5..0000000000 --- a/changelog.d/added-maintainer-notes.md +++ /dev/null @@ -1 +0,0 @@ -- **Maintainer notes on the Activity Monitor.** With more than one maintainer running a hive, there was nowhere on the dashboard to leave a colleague a word about an item short of a GitHub comment everyone else could read. Each row now carries a 🗒 button with a count badge: click it for the item's maintainer notes — who wrote what, when — and a one-line composer (⌘/Ctrl+Enter). Notes are stored on the spoke in the append-only `/data/maintainer-notes.jsonl` and are never written to GitHub; every signed-in maintainer sees them, adding one takes write on the repo, deleting is author-or-owner, and the `maintainer-notes` SSE frame keeps the other browsers live. The scheduler types an item's notes into the agent's kick under `# Maintainer notes` (1 KB cap), so what a maintainer wrote on the row reaches whoever picks it up. `GET`/`POST /api/notes`, `DELETE /api/notes/{id}`; audited as `maintainer_note_add` / `maintainer_note_delete`.