From 25ec79d56eeb6dce84cbba7b8bf0db54e2d477b8 Mon Sep 17 00:00:00 2001 From: hive-release-bot Date: Sat, 7 Nov 2026 20:35:19 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=96=20release:=20v5.188.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.188.0 entry. See src/docs/releases.md. Signed-off-by: hive-release-bot --- CHANGELOG.md | 17 +++++++++++++++++ changelog.d/added-agent-cli-memory-config.md | 1 - changelog.d/added-knowledge-advisor.md | 1 - changelog.d/added-knowledge-entry-scope.md | 1 - .../changed-review-backlog-min-severity.md | 1 - changelog.d/fixed-agentsmd-hosted-fallback.md | 1 - changelog.d/fixed-release-tag-built-ancestor.md | 1 - 7 files changed, 17 insertions(+), 6 deletions(-) delete mode 100644 changelog.d/added-agent-cli-memory-config.md delete mode 100644 changelog.d/added-knowledge-advisor.md delete mode 100644 changelog.d/added-knowledge-entry-scope.md delete mode 100644 changelog.d/changed-review-backlog-min-severity.md delete mode 100644 changelog.d/fixed-agentsmd-hosted-fallback.md delete mode 100644 changelog.d/fixed-release-tag-built-ancestor.md diff --git a/CHANGELOG.md b/CHANGELOG.md index a06edcd27e..e952b76531 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,23 @@ Hive did not historically maintain a complete changelog. This file starts a prag ## Unreleased +## 2026-11-07 (v5.188.0) + +### Added + +- New `agents.cli_memory` block (per-agent `cli_memory:` override): `auto_memory` (default false) pins Claude Code / Codex / Copilot CLI auto-memory off via `CLAUDE_CODE_DISABLE_AUTO_MEMORY=1`, `[features] memories = false` and `"memory": false`; `clear_on_kick` wipes that agent's `~/.claude/projects/*/memory`, `$CODEX_HOME/memories*` and `~/.gemini/GEMINI.md` before each non-resume kick (hivecommons/hive#17032). +- Mid-task knowledge advisor (opt-in `knowledge.advisor`, default off): when a running agent's work enters a scope that was not on screen at kick time, the matching knowledge entries the kick did not already carry are typed into its session as one `📚 Knowledge:` line each, capped per kick (`knowledge.advisor_max_per_kick`), never during a tool call, with per-agent opt-out (`knowledge.advisor_exclude_agents`) and a `knowledge-advisor` prompt-history trigger for measurement (#17052) +- Knowledge entries can carry a `scope:` frontmatter block (`paths`, `labels`, `lanes`); the kick primer surfaces a scoped entry only when the kick's lane, issue labels or known file paths match, so repository facts are injected on demand instead of on every kick (#17045). + +### Changed + +- Review backlog: findings below the new `review.backlog.min_severity` (default `P2`) are no longer filed as issues but collected in one upserted `hive:review-followups` comment on the PR; the issue cap `review.backlog.max_per_pr` (default 3) now applies over the PR's lifetime instead of per day (`max_per_pr_per_day` is a retired alias); and new findings sharing a perspective are filed as one checklist item. Set `min_severity: P3` to file every finding as before (hivecommons/hive#17065). + +### Fixed + +- Hosted spokes now inject the primary repo's `AGENTS.md` into kicks: when neither `project.checkouts_dir` nor a matching `policies.local_dir` names a local checkout, the scheduler fetches `AGENTS.md` from the repo's default branch through the hive's GitHub client (15-minute cache, last-known-good on API failure, same injection cap) and materialises it under `/data/agentsmd-cache///` so the log shows `agentsmd: injecting repo instructions into kick` with that root ([#17090](https://github.com/hivecommons/hive/issues/17090)). +- Tagged Release no longer stands down when `v5` advances past the commit `docker.yml` built. The version tag now names the release commit parented on that built SHA (the retagged images' exact tree plus the changelog), the release lands on `v5` as a merge commit even when the tip has moved, and the hourly backstop releases the newest built ancestor of the tip instead of requiring the tip itself; `docker.yml` push builds also get their own concurrency slot so a merge burst no longer cancels them. Under merges faster than a multi-arch build the old "defer to the successor" rule had no terminating condition and left `v5` untagged from `v5.186.4` (2026-10-18) onward. + ## 2026-11-07 (v5.187.0) ### Added diff --git a/changelog.d/added-agent-cli-memory-config.md b/changelog.d/added-agent-cli-memory-config.md deleted file mode 100644 index eb3be2be7c..0000000000 --- a/changelog.d/added-agent-cli-memory-config.md +++ /dev/null @@ -1 +0,0 @@ -- New `agents.cli_memory` block (per-agent `cli_memory:` override): `auto_memory` (default false) pins Claude Code / Codex / Copilot CLI auto-memory off via `CLAUDE_CODE_DISABLE_AUTO_MEMORY=1`, `[features] memories = false` and `"memory": false`; `clear_on_kick` wipes that agent's `~/.claude/projects/*/memory`, `$CODEX_HOME/memories*` and `~/.gemini/GEMINI.md` before each non-resume kick (hivecommons/hive#17032). diff --git a/changelog.d/added-knowledge-advisor.md b/changelog.d/added-knowledge-advisor.md deleted file mode 100644 index 0f17a693d3..0000000000 --- a/changelog.d/added-knowledge-advisor.md +++ /dev/null @@ -1 +0,0 @@ -- Mid-task knowledge advisor (opt-in `knowledge.advisor`, default off): when a running agent's work enters a scope that was not on screen at kick time, the matching knowledge entries the kick did not already carry are typed into its session as one `📚 Knowledge:` line each, capped per kick (`knowledge.advisor_max_per_kick`), never during a tool call, with per-agent opt-out (`knowledge.advisor_exclude_agents`) and a `knowledge-advisor` prompt-history trigger for measurement (#17052) diff --git a/changelog.d/added-knowledge-entry-scope.md b/changelog.d/added-knowledge-entry-scope.md deleted file mode 100644 index 9333086697..0000000000 --- a/changelog.d/added-knowledge-entry-scope.md +++ /dev/null @@ -1 +0,0 @@ -- Knowledge entries can carry a `scope:` frontmatter block (`paths`, `labels`, `lanes`); the kick primer surfaces a scoped entry only when the kick's lane, issue labels or known file paths match, so repository facts are injected on demand instead of on every kick (#17045). diff --git a/changelog.d/changed-review-backlog-min-severity.md b/changelog.d/changed-review-backlog-min-severity.md deleted file mode 100644 index 5cc630a683..0000000000 --- a/changelog.d/changed-review-backlog-min-severity.md +++ /dev/null @@ -1 +0,0 @@ -- Review backlog: findings below the new `review.backlog.min_severity` (default `P2`) are no longer filed as issues but collected in one upserted `hive:review-followups` comment on the PR; the issue cap `review.backlog.max_per_pr` (default 3) now applies over the PR's lifetime instead of per day (`max_per_pr_per_day` is a retired alias); and new findings sharing a perspective are filed as one checklist item. Set `min_severity: P3` to file every finding as before (hivecommons/hive#17065). diff --git a/changelog.d/fixed-agentsmd-hosted-fallback.md b/changelog.d/fixed-agentsmd-hosted-fallback.md deleted file mode 100644 index 6b70e6c3ed..0000000000 --- a/changelog.d/fixed-agentsmd-hosted-fallback.md +++ /dev/null @@ -1 +0,0 @@ -- Hosted spokes now inject the primary repo's `AGENTS.md` into kicks: when neither `project.checkouts_dir` nor a matching `policies.local_dir` names a local checkout, the scheduler fetches `AGENTS.md` from the repo's default branch through the hive's GitHub client (15-minute cache, last-known-good on API failure, same injection cap) and materialises it under `/data/agentsmd-cache///` so the log shows `agentsmd: injecting repo instructions into kick` with that root ([#17090](https://github.com/hivecommons/hive/issues/17090)). diff --git a/changelog.d/fixed-release-tag-built-ancestor.md b/changelog.d/fixed-release-tag-built-ancestor.md deleted file mode 100644 index 860a32c817..0000000000 --- a/changelog.d/fixed-release-tag-built-ancestor.md +++ /dev/null @@ -1 +0,0 @@ -- Tagged Release no longer stands down when `v5` advances past the commit `docker.yml` built. The version tag now names the release commit parented on that built SHA (the retagged images' exact tree plus the changelog), the release lands on `v5` as a merge commit even when the tip has moved, and the hourly backstop releases the newest built ancestor of the tip instead of requiring the tip itself; `docker.yml` push builds also get their own concurrency slot so a merge burst no longer cancels them. Under merges faster than a multi-arch build the old "defer to the successor" rule had no terminating condition and left `v5` untagged from `v5.186.4` (2026-10-18) onward.