Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
36 commits
Select commit Hold shift + click to select a range
03094ce
✨ crux: contained run service with saved run state (S2 + S7 minimum) …
clubanderson Nov 7, 2026
eac7f88
πŸ› fix(ci): re-validate policy checks before replaying a native-queue-…
hivecommons-hive[bot] Nov 7, 2026
2ecfb71
πŸ› fix(kubejob): do not mount the SA token into contained runs and nev…
hivecommons-hive[bot] Nov 7, 2026
92cd2af
πŸ“– docs: proxy override reflects #16785/#16895 behaviour (#17034)
clubanderson Nov 7, 2026
7a92935
🌱 build(deps): bump ws from 8.21.3 to 8.22.1 in /src/proxy (#16567)
dependabot[bot] Nov 7, 2026
912b2eb
πŸ“– docs: how Hive injects knowledge and memory into agents (#17042)
clubanderson Nov 7, 2026
53c7877
πŸ› hub: fall back to other pools when Auto-pick's preferred pool has n…
clubanderson Nov 7, 2026
aad9429
πŸ› fix(dashboard): Hold works when the hive's hold label exceeds GitHu…
clubanderson Nov 7, 2026
49ff2e4
🌱 AGENTS.md: keep tone and workflow rules; move repository facts into…
clubanderson Nov 7, 2026
1f9680f
✨ kick priming: one log line per kick with knowledge bytes injected a…
clubanderson Nov 7, 2026
943d807
πŸ› agents: give each agent its own CLI memory β€” stop bridging .claude/…
clubanderson Nov 7, 2026
d6c63af
🌱 automerge: upsert signoff-attribution and unauthorized comments ins…
clubanderson Nov 7, 2026
e8347bd
✨ knowledge advisor: surface scoped knowledge mid-task when an agent'…
clubanderson Nov 7, 2026
dc4f20c
πŸ› release: tag the built commit instead of deferring when v5 advances…
clubanderson Nov 7, 2026
0485b71
✨ knowledge: scope block on entries and a kick-context filter in the …
clubanderson Nov 7, 2026
03d1ac1
✨ review backlog: min_severity floor, per-PR lifetime cap, collapse s…
clubanderson Nov 7, 2026
bde11aa
πŸ› fix(ci): native-queue-policy accepts prow dco for v5-reachable sync…
hivecommons-hive[bot] Nov 7, 2026
cc4b8eb
πŸ”– release: v5.187.0
actions-user Nov 7, 2026
21bd634
πŸ› scheduler: fetch AGENTS.md from GitHub when a hosted spoke has no l…
clubanderson Nov 7, 2026
ec3d6fe
Merge pull request #17094 from hivecommons/release-gate/v5.187.0
clubanderson Nov 7, 2026
c649246
✨ agents: CLI auto-memory off by default; clear_memory_on_kick wipes …
clubanderson Nov 7, 2026
e4cc8e4
πŸ“– docs(design): drain CLI auto-memory into draft knowledge beads (#17…
hivecommons-hive[bot] Nov 7, 2026
ad3ffa6
πŸ› fix(issue-claims): classify exhausted claim side-effect failures (#…
hivecommons-hive[bot] Nov 7, 2026
eb1bd50
✨ knowledge: prime an agent's own drafts when agent_scopes.include_st…
clubanderson Nov 7, 2026
25ec79d
πŸ”– release: v5.188.0
actions-user Nov 7, 2026
484f649
πŸ“– docs(crux): document --runs-config and /v1/runs; refresh work-servi…
hivecommons-hive[bot] Nov 7, 2026
9f04cc7
Merge pull request #17100 from hivecommons/release-gate/v5.188.0
clubanderson Nov 7, 2026
dce861a
πŸ”– release: v5.189.0
actions-user Nov 7, 2026
30468b7
Merge pull request #17108 from hivecommons/release-gate/v5.189.0
clubanderson Nov 7, 2026
2d96de7
πŸ› docs(changelog): drop literal [open](url) placeholder that fails th…
hivecommons-hive[bot] Nov 7, 2026
13b3f04
πŸ“ proposal: LLM-ranked knowledge advisor (phase 2 of #17052) (#17107)
hivecommons-hive[bot] Nov 7, 2026
86830fc
🌱 contributor-nudge once per PR+reason; fold origin notes into status…
clubanderson Nov 7, 2026
8a06dda
πŸ› fix(crux/checkout): match the repo allowlist on segment boundaries …
hivecommons-hive[bot] Nov 7, 2026
bde4411
✨ release: make v6 an official release line (v6.x.y tags) (#17074)
clubanderson Nov 7, 2026
6888c77
🌱 Merge origin/v5 into v6: v6 release line cut (v6.x.y tags)
clubanderson Nov 7, 2026
e2d3260
🌱 ci: native-queue contract test resolves the pin against release_lines
clubanderson Nov 7, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
162 changes: 82 additions & 80 deletions .github/release-lines.yml
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,14 @@
# channel rows, default branch, docs) is the checklist in
# src/docs/release-line-guard.md.

# The release lines CI is expected to cover.
release_lines: [v4, v5]
# The release lines CI is expected to cover. v6 was cut as a release line on
# 2026-11-07: it mints `v6.x.y` tags, GitHub Releases and SBOMs through
# tagged-release.yml like v5 does. Channel ownership did NOT move with it β€”
# v5 still publishes `candidate` + `:latest` and owns `stable` (promoted from
# the default branch by promote-stable.yml); v6 publishes `edge` + `v6-latest`
# (its own docker.yml rows). See src/docs/release-line-guard.md, "Cutting a
# new release line", and src/docs/releases.md.
release_lines: [v4, v5, v6]

# Workflows whose branch filters are pinned to the release lines.
#
Expand All @@ -52,67 +58,62 @@ pinned:
# sunset, and a PR targeting v2 runs the v2 merge-ref's workflows anyway,
# where this file does not exist. Same excluded-not-backfilled reasoning as
# docs-link-check.yml below.
# v6 is carried as an EXTRA on the workflows below rather than added to
# `release_lines`: it is the #7563 development line and has not been cut as
# a release line β€” until it is, the release workflows refuse to tag or
# promote from it (#9154). What it DOES need is the same PR
# gating as v4, because feature PRs target it directly (spine, mention
# triggers); without these extras a v6-base PR runs no Go build, test, or
# security lane at all. It is ALSO published β€” `v6-latest` and, once its own
# docker.yml rows say so, the `edge` channel (#7721 Phase 1) β€” which is the
# `env_lists` extra below, not a `release_lines` entry: publishing a line's
# image is a narrower commitment than covering it with every pinned lane.
changelog-fragment-guard.yml: [v5, v6]
# v6 used to be carried as an EXTRA on the PR-gating workflows below while
# it was the #7563 development line; since its cut (2026-11-07) it is a
# `release_lines` entry, so the extras are gone and every pinned lane that
# does not write down a `-v6` exclusion covers it.
changelog-fragment-guard.yml: []
# Static analysis and vulnerability scanning for the Go module. Pinned to the
# release lines and nothing else: a feature branch gets the same gate through
# `pull_request`, and running it on every pushed branch would burn runner
# minutes re-scanning code that has not reached a release line.
# Added with the docs link checker (#5278), after the v2 line was sunset
# (#5030-era). It gates src/docs/ links on the release lines plus the v6
# development line (#9476): v6 takes doc changes through feature PRs like
# the other lines, and without this extra a v6-base PR's broken doc links
# and stale code citations landed ungated. v2 was never back-filled: the
# workflow never ran there and the line is retired.
docs-link-check.yml: [v6]
# Post-merge DCO monitor for protected branch history. It intentionally
# watches v4 and v5 only: v4 is the source line whose Tide squash commits
# triggered #6312, and v5 is the sync target that inherits those commits.
dco-post-merge.yml: [v5]
# Push-scoped delta DCO gate (#6756). Same v4/v5 coverage and reasoning as
# dco-post-merge.yml above: v4 is the line whose pushes it audits, v5 the
# sync target inheriting them; v2 is sunset and takes no pushes.
dco-push-delta.yml: [v5]
# FOSSA license scanning runs on the active CNCF onboarding line only;
# v4 is feature-frozen and not being imported as the initial Hive Commons
# CNCF FOSSA project.
fossa.yml: [-v4]
# GitHub Actions Workflow triage compiles only on the active v5 line; older
# release lines do not carry the gh-aw automation surface.
gh-aw-compile.yml: [-v4]
# (#5030-era). It gates src/docs/ links on every release line (#9476): v6
# takes doc changes through feature PRs like the other lines, and without
# it a v6-base PR's broken doc links and stale code citations landed
# ungated. v2 was never back-filled: the workflow never ran there and the
# line is retired.
docs-link-check.yml: []
# Post-merge DCO monitor for protected branch history. It watches every
# release line: v4 is the source line whose Tide squash commits triggered
# #6312, and v5 and v6 are the sync targets that inherit those commits.
dco-post-merge.yml: []
# Push-scoped delta DCO gate (#6756). Same coverage and reasoning as
# dco-post-merge.yml above: v4 is the line whose pushes it audits, v5 and
# v6 the sync targets inheriting them; v2 is sunset and takes no pushes.
dco-push-delta.yml: []
# FOSSA license scanning runs on the CNCF onboarding line only: the Hive
# Commons FOSSA project is imported from ONE branch, v5. v4 is
# feature-frozen; v6 inherits v5's dependency set through the top-ups and
# is not a second FOSSA project.
fossa.yml: [-v4, -v6]
# GitHub Actions Workflow triage compiles only on the default v5 line, where
# the gh-aw agentic workflows are registered; v4 does not carry the gh-aw
# automation surface and v6 only mirrors v5's compiled lock files.
gh-aw-compile.yml: [-v4, -v6]
# Self-test for the hive-action-smoke dispatch workflow (#12964). Its push
# trigger names v5 only: the smoke workflow is registered on v5 and does not
# exist on the feature-frozen v4 line, so there is nothing there to test.
hive-action-smoke-tests.yml: [-v4]
go-security-analysis.yml: [v5, v6]
# v6 carries its own action unit gate (hive-action-tests.yml, v6 only).
hive-action-smoke-tests.yml: [-v4, -v6]
go-security-analysis.yml: []
# Unit gate for the reusable hive action's app-handle helper (#9707). The
# action and its smoke wiring live only on the v6 development line, so the
# push filter watches v6 alone; v4 is feature-frozen and v5 never carried
# the action, hence the explicit exclusions.
hive-action-tests.yml: [v6, -v4, -v5]
# action and its smoke wiring live only on the v6 line, so the push filter
# watches v6 alone; v4 is feature-frozen and v5 never carried the action,
# hence the explicit exclusions.
hive-action-tests.yml: [-v4, -v5]
# Headless phone-viewport sweep of the Hive Chat panel (#11852). The chat
# panel, its chip lists and the sweep script live only on the v6 development
# line, so its pull_request filter watches v6 alone; v4 is feature-frozen and
# v5 never carried the panel, hence the explicit exclusions.
hive-chat-phone-sweep.yml: [v6, -v4, -v5]
# panel, its chip lists and the sweep script live only on the v6 line, so
# its pull_request filter watches v6 alone; v4 is feature-frozen and v5
# never carried the panel, hence the explicit exclusions.
hive-chat-phone-sweep.yml: [-v4, -v5]
# promtool check + unit tests for the monitoring component's PrometheusRule
# (#15438). The component exists only on the v6 development line; v4 is
# feature-frozen and v5 never carried it, hence the explicit exclusions.
prometheusrule-check.yml: [v6, -v4, -v5]
# (#15438). The component exists only on the v6 line; v4 is feature-frozen
# and v5 never carried it, hence the explicit exclusions.
prometheusrule-check.yml: [-v4, -v5]
# Renders every kustomize overlay, plus the monitoring component (#15503).
# Same v6-only reasoning as prometheusrule-check.yml: the component exists
# only on the v6 development line; v4 is feature-frozen and v5 never
# carried it, hence the explicit exclusions.
kustomize-render.yml: [v6, -v4, -v5]
# Same v6-only reasoning as prometheusrule-check.yml.
kustomize-render.yml: [-v4, -v5]
podman-arm64-lane.yml: []
podman-contract.yml: []
podman-rootful-lane.yml: []
Expand Down Expand Up @@ -145,46 +146,48 @@ pinned:
# They react to PRs into, and pushes to, the lines that take feature PRs:
# v5 (stable + candidate) and v6 (edge). v4 is feature-frozen and takes no
# new PRs, so there is nothing there to order or refresh.
pr-overlap.yml: [v6, -v4]
pr-auto-update.yml: [v6, -v4]
pr-auto-update-test.yml: [v6, -v4]
pr-overlap.yml: [-v4]
pr-auto-update.yml: [-v4]
pr-auto-update-test.yml: [-v4]
# Native queue admission is available on the active feature lines only.
# This is CI coverage, not an opt-in or a queue rule for either branch.
native-queue-policy.yml: [v6, -v4]
testutil-guard.yml: [v5, v6]
v2-ci.yml: [v5, v6]
v2-tests.yml: [v5, v6]
native-queue-policy.yml: [-v4]
testutil-guard.yml: []
v2-ci.yml: []
v2-tests.yml: []
# Automated v4 -> v5 forward-merge cadence (#7297). Its only branch filter is
# the `workflow_run` trigger, which names the line whose RELEASES it reacts
# to β€” v4, the source of every top-up. v2 is sunset and cuts no releases to
# carry forward, and v5 is the merge TARGET rather than a trigger, so it is
# not a branch this workflow watches (on v5, where v5 is itself a release
# line, it must be excluded explicitly for the same reason).
v5-topup.yml: [-v5]
# not a branch this workflow watches (v5 and v6 are release lines too, so
# they must be excluded explicitly for the same reason β€” v6 reaches v4's
# releases through v5).
v5-topup.yml: [-v5, -v6]
# Post-freeze intake gate for v4 (#7693, runbook Β§2). It watches PRs into
# the ONE line the accepted freeze policy (#6346) applies to; v2 is sunset
# and takes no PRs, and v5/v6 are exactly where non-critical work is sent.
v4-freeze-gate.yml: [-v5]
v4-freeze-gate.yml: [-v5, -v6]
# Automated v5 -> v6 forward-merge cadence (#7563, Track 7). Its only branch
# filter is the `push` trigger naming the line whose MOVEMENT it reacts to β€”
# v5, the source of every v6 top-up. v2 and v4 are excluded for the same
# reason as v5-topup.yml's exclusions: they are not the branch this workflow
# watches (v4 reaches v6 through v5), and v6 is the merge TARGET, not a
# trigger.
v6-topup.yml: [v5, -v4]
# v5, the source of every v6 top-up. v4 is excluded for the same reason as
# v5-topup.yml's exclusions: it is not the branch this workflow watches (v4
# reaches v6 through v5), and v6 is the merge TARGET, not a trigger.
v6-topup.yml: [-v4, -v6]
# Publishes src/crux to hivecommons/crux (#14138). It watches the ONE line
# the published module is cut from β€” v5, where the nested module lives and
# where `crux/vX.Y.Z` tags are made. v4 is feature-frozen and has no
# src/crux; publishing from two lines would race on hivecommons/crux main.
crux-sync.yml: [-v4]
# src/crux; v6 carries a copy through the top-ups but publishing from two
# lines would race on hivecommons/crux main.
crux-sync.yml: [-v4, -v6]
# Nightly + path-filtered Forgejo smoke (#14116). Its push/pull_request
# filters name v5 only: the forge.Merger it exercises lives on v5, and v4 is
# feature-frozen.
forgejo-smoke.yml: [-v4]
# filters name v5 only: it exercises the forge.Merger against a live Forgejo
# and one line's coverage is enough for a shared package β€” v6 inherits the
# package through the top-ups, and v4 is feature-frozen.
forgejo-smoke.yml: [-v4, -v6]
# Publishes the headless Twitch streamer image (#15594) from v5 only: the
# dashboard's `?kiosk=1` mode it depends on lives on v5 and v4 is
# feature-frozen. The image is operator tooling, not a hive release channel.
stream-image.yml: [-v4]
# image is operator tooling, not a hive release channel, so it follows the
# default branch rather than every release line; v4 is feature-frozen.
stream-image.yml: [-v4, -v6]

# Workflows that deliberately do NOT pin to the release lines. Each must keep a
# wildcard branch filter; if one is ever narrowed to a fixed list, the guard
Expand Down Expand Up @@ -212,11 +215,10 @@ env_lists:
# docker.yml's gate job: only long-lived branches push to GHCR. `mk` and `dd`
# are standing experimental branches β€” not release lines, but branches a hive
# can be assigned to, so they legitimately publish a `<branch>-latest` tag.
# `v6` is the #7563 development line, published so the `edge` channel can be
# re-based on it (#7721 Phase 1): `v6-latest` must exist before v6's own
# docker.yml publish rows can point `edge` at it. Every release branch that
# carries this list names v6 here, so the guard agrees across lines.
docker.yml LONG_LIVED: [mk, dd, v6]
# `v6` used to be an extra here while it was the #7563 development line
# (published so the `edge` channel could be re-based on it, #7721 Phase 1);
# since its cut it is a release line and covered without an extra.
docker.yml LONG_LIVED: [mk, dd]

# MAINTAINER DECISION (#4405, answered by #8061 on 2026-09-21): `v2` is retired.
# It was removed from `release_lines`, from every workflow that named it, and
Expand Down
2 changes: 1 addition & 1 deletion .github/scripts/integration-governance.cjs
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ const MAX_COMMITS = 1000;
const MAX_AUTHOR_BATCH = 50;
// This literal is inside the enrolled .github closure. A caller-supplied
// preparedBy.sourceSHA must never choose a new executable verifier tree.
const TRUSTED_SCRIPTS_TREE = '267924f87d77a3fa335accce1b0c74d1a5cfdab8';
const TRUSTED_SCRIPTS_TREE = '23eed03bebbb82deb0128f396b551939326729f2';
const SOURCE = 'https://github.com/kubernetes-sigs/kubebuilder-release-tools/tree/012269a88fa4c034a0acf1ba84c26b195c0dbab4';
const sha = value => crypto.createHash('sha256').update(value).digest('hex');
const git = (args, cwd = process.cwd()) =>
Expand Down
Loading
Loading