Repository navigation
docs: releases are owner-approved — agents propose, never cut version branches (#2910) - #2919
Merged
Merged
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.3248-pr.2919.fd1922fThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2919.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner
Author
[bot] 🏷 已核对完成 — PR #2919 已存在且实现正确,无需重做,也未另开重复 PR。 本条 ework 项即 GitHub PR #2919(head 核对结果:
结构化八问(docs-only):
判定:可合并。 仅剩人工合并这一步(agent 不合并不 publish)。请在此 PR 上合并:#2919 |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.331-master.7065dfc # this exact build
npm install -g billion-context@master # always the newest merged build
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the owner rule 「禁止私自提交版本分支」(2026-10-12) to the two operative sections of AGENTS.md:
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.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 authoredework-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).