Repository navigation
[PR] ci(#4828): kernel-guard exempts lockfile-only churn from the human gate - #4837
Merged
Merged
Conversation
…n for lockfile-only churn kernel/package-lock.json is generated state, not kernel source. Agents' test prep (npm install inside kernel/, sweep-bot merges of stale lockfiles) churns it without any intent to change the kernel — 8 PRs (#4823 #4808 #4802 #4800 #4799 #4794 #4790 #4785) tripped the human gate on lockfile-only diffs, and the previous stopgap (bots appending kernel-change: declarations to PR bodies) was correctly rejected by the owner as bypassing the approval step. The human gate exists to protect kernel SOURCE. Rule 1 now ignores kernel/package-lock.json when deciding whether a PR 'touches kernel/'; real source/build-config changes still require the declaration + owner approval, and lockfile CONSISTENCY stays enforced by the separate lock-sync job (which fails on genuine drift — the #4725 merge red being today's live proof).
ranxianglei
changed the title
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6239-pr.4837.20ddf94This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4837.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.860-master.24e71f6 # this exact build
npm install -g billion-context@master # always the newest merged build
|
ranxianglei
pushed a commit
to yanhuojiyusheng/billion-context
that referenced
this pull request
Oct 26, 2026
…4856 review) The author's rebase landed on 05c379e; master has since advanced via ranxianglei#4837 (kernel-guard lockfile exemption). Additive sync per AGENTS §7.2 — no history rewrite.
This was referenced Oct 26, 2026
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.
(ai: zhipuai-lb/glm-5.3)
Fixes #4828
这是什么
kernel-guard 的人工门禁(Rule 1)把
kernel/package-lock.json也算进「改了 kernel/」——而它是生成物,不是 kernel 源码。8 个 PR(#4823 #4808 #4802 #4800 #4799 #4794 #4790 #4785)纯粹因为锁文件漂移被卡,机器人往 PR 正文补kernel-change:声明的做法又被 owner 正确地否决了(绕过了批准环节)。修法(= issue 里方案 A 的机制化,一次治一类而不是逐个批准)
Rule 1 判定「触碰 kernel/」时排除
kernel/package-lock.json:验证
对 #4828 问题的直接回答
owner 不再需要逐个批准这批锁文件更新:本 PR 合并后,那 8 个 PR 重跑 CI 即绿,无需任何声明。代理侧的纪律(别在 PR 分支里对 kernel/ 跑 install)仍值得写进 AGENTS.md,但门禁不再依赖人的自觉。