diff --git a/CHANGELOG.md b/CHANGELOG.md index 4b36b59320..2ed82639bf 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -73,6 +73,13 @@ Hive did not historically maintain a complete changelog. This file starts a prag ### Fixed - release: cap GitHub Release notes at `RELEASE_NOTES_MAX_CHARS` (120000) before the SBOM/NOTICE trailer, cutting the changelog section at a bullet boundary and linking the tag's full `CHANGELOG.md` section, so a first-on-the-line release such as v6.0.0 no longer fails `gh release create` with HTTP 422 "body is too long" after the tag and image retags have landed. +## 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`.