Skip to content

docs: releases are owner-approved — agents propose, never cut version branches (#2910) - #2919

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-12_release-owner-approval
Oct 12, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-12_release-owner-approval

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

What

Adds the owner rule 「禁止私自提交版本分支」(2026-10-12) to the two operative sections of AGENTS.md:

  1. §4 Git Safety Rules — new table row NEVER cut a release without owner approval: release branches (*_release-v*, *_release-kernel-v*, bugfix-release/*) and release PRs are opened ONLY after the owner explicitly approves in-thread (「发版 vX」). Agents may propose a release (what's stranded on master, who's blocked) but never push the branch or open the PR. Includes the standard refusal reply.
  2. §5 Release Workflow — new first hard-rule bullet Owner-approved start: steps 1–6 run only after owner approval; triage that ends at "fix stranded on master, users blocked" proposes the release in-thread and stops. Records the origin.

Why

Origin #2906 → #2910: during triage of a duplicate report, a bot autonomously decided npm v0.1.195 lacked the fix, cut branch 2026-10-12_release-v0.1.196 (commit authored ework-agent <ework-agent@users.noreply.github.com>), and opened release PR #2910 — 13 minutes after the issue was filed, with no human in the loop.

Every mechanical rule held (no npm publish, no self-merge, correct branch naming, version touched only on the release branch, guards skipped by design) — what was missing is a rule that the decision to ship belongs to the owner. This PR closes that gap: agents propose, the owner dispatches.

Scope

Docs-only, +2 lines in AGENTS.md; no functional change. Same shape as #2911 (version-first triage rule).

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-12_release-owner-approval (14bac44)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.3248-pr.2919.fd1922f

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr2919.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 已核对完成 — PR #2919 已存在且实现正确,无需重做,也未另开重复 PR。

本条 ework 项即 GitHub PR #2919(head 2026-10-12_release-owner-approval @ 14bac449,base master,+2/-0,单文件 AGENTS.md)的镜像,其内容已精确落地本项所述改动。按 loop guard(一项至多一 PR),我没有重切分支或再开第二个 PR。

核对结果:

  • §4 Git Safety Rules — 新增表格行 NEVER cut a release without owner approval:发布分支(*_release-v* / *_release-kernel-v* / bugfix-release/*)与发布 PR 仅在 owner 于线程内明确批准(「发版 vX」/「批准发布」)后方可开启;agent 可以提议(master 上卡了什么、谁被阻塞、建议版本号)但绝不自行 push 分支或开 PR;含标准拒绝话术;标注 owner rule 2026-10-12 / release v0.1.196 #2910。✅
  • §5 Release Workflow — 新增首条硬规则 Owner-approved start:步骤 1–6 仅在 owner 批准后执行;triage 若落到「fix 卡在 master、用户被阻塞」则在线程内提议后停下——发什么、何时发归 owner;记录起源 acf delegates lost on pi /new #2906 → bot 擅自切 v0.1.196(release v0.1.196 #2910),当时所有机械规则都守住了(不 publish/不自合/命名规范/版本只在发布分支改),但「要不要发版」这个决策从来不该是 bot 做的。✅
  • 纯文档改动,无功能 / 配置 / wire / 版本变更。
  • CI 全绿:18/18 通过(test ubuntu/windows ×22/24、static-gates、kernel-guard、version-guard、config-surface-guard、docs-sync、docs-coverage、lane-guard、lock-sync、pi-subagents-guard、unused-exports、build-artifact);mergeable 干净。

结构化八问(docs-only):

  1. 是什么问题:发版「决策权」缺位——release v0.1.196 #2910 里 bot 在 triage 期间擅自切了 v0.1.196 版本分支并开 PR,全程无人参与。
  2. 什么原因导致的:既有规则只约束机械动作(不 publish、不自合、分支命名、版本只在发布分支改),却没有一条规定「是否发版」这个决策归属 owner。
  3. 影响范围与严重程度:流程/治理层面;不影响任何用户功能或运行时行为,纯文档。
  4. 怎么修复的:在 AGENTS.md 两个操作节各加一行——§4 表格行 + §5 首条硬规则,统一为「agent 只提议、owner 拍板后才切分支/开 PR」。
  5. 是否有回归问题:不涉及(无代码路径触碰)。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及(补治理规则,不改架构边界)。
  8. 是否引入新配置:不涉及。

判定:可合并。 仅剩人工合并这一步(agent 不合并不 publish)。请在此 PR 上合并:#2919

@ranxianglei
ranxianglei merged commit 7065dfc into master Oct 12, 2026
18 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.331-master.7065dfc (rolling master tag).

npm install -g billion-context@0.0.331-master.7065dfc  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

@ranxianglei
ranxianglei deleted the 2026-10-12_release-owner-approval branch October 15, 2026 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant