Repository navigation
[PR] kernel: sync package-lock.json to 0.0.136 (lock left at 0.0.133 by the bump chain) - #3782
Conversation
The 0.0.134→0.0.136 bumps (#3759/#3767) updated kernel/package.json and the root lock's workspace entry but never regenerated kernel/package-lock.json — the same dual-lock drift #3658 hit. npm ci inside kernel/ would refuse (lock does not satisfy package.json). Regenerated with npm install --package-lock-only; no source changes.
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4477-pr.3782.db5eab7This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3782.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复。 open+closed 的 issue 与 PR(近 7 天为主,按失败签名「kernel lock 0.0.133/0.0.136」匹配)无其他同型条目;本条目即上游 PR #3782 的镜像,无并行工作项。 标签: bug / scope/ci / p3(缺陷类;构建与 CI 域的锁文件漂移;内部簿记问题、无运行时影响)。 审核结论(独立复核,非复读 issue 描述)已核实的部分:
需要更正的一处(issue 描述过重):「在 kernel/ 里跑 层次判断(症状 vs 机制): 表面是「#3767 漏刷了锁」,但机制层有个结构缺口——已有的 #2704 已在 PR 分支补一个标注 commit CI 状态(审核时点):9 success / 12 skipped(e2e 车道,纯锁文件变更的预期跳过)/ 9 queued(含 lock-sync 本身),无失败。补推后新 run 会带上扩展后的 gate。 八问
收工判定:代码层面可合(diff 已独立验证正确、gate 双向验证),待补推后的 queued 车道(含扩展版 lock-sync)转绿即可由人工合并;合并动作归人。 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.599-master.96c6598 # this exact build
npm install -g billion-context@master # always the newest merged build
|
The lock-sync CI lane (#3782) also enforces the kernel's own lockfile; the 0.0.151 -> 0.0.152 bump in kernel/package.json left it stale.
The PR bumped kernel/package.json to 0.0.161 but neither lockfile was regenerated, leaving the root lock recording acp-kernel 0.0.159. The lock-sync gate (#2704/#3782) regens both locks and fails on any drift. This staleness already existed on master (kernel 0.0.160 vs root lock 0.0.159); the bump merely widened it. Pure version-line regen, no structural churn. Un-blocks the `test` lane.
…issed them) f7d5e86 (#4292) bumped in-repo kernel/package.json to 0.0.160 without regenerating either lockfile, so both still recorded 0.0.159: - package-lock.json: the "kernel" file:-link entry's version - kernel/package-lock.json: its own top-level + packages."" version The lock-sync gate (npm install --package-lock-only + diff, run for BOTH lockfiles per #3782) fails on every head until these recorded resolutions match. Mechanical sync only — no kernel source change.
The dryRun-gate commit bumped kernel/package.json to 0.0.162 without regenerating the kernel lockfile (last synced to 0.0.161). Regenerated via npm install --package-lock-only; idempotent, version line only.
The PR bumped pi-subagents/package.json 0.2.3 -> 0.2.4 but did not regenerate the root package-lock.json, which still recorded the file: link at 0.2.3. The lock-sync drift guard (#2704/#3782) regenerates the root lock and fails on any residual diff, so the check went red. Regenerating updates exactly one line: the billion-context-pi-subagents version record 0.2.3 -> 0.2.4. Kernel lock verified clean (the PR does not touch kernel/).
Rebase onto master moved the kernel bump from 0.0.182 to 0.0.186 (master had advanced to 0.0.185 via bcda253); regenerate root + kernel lockfiles with the exact CI lock-sync commands so the gate is green at this head.
Rebase onto master moved the kernel bump from 0.0.186 to 0.0.193 (master had advanced to 0.0.192); regenerate root + kernel lockfiles with the exact CI lock-sync commands so the gate is green at this head.
The PR bumped pi-subagents/package.json 0.2.3 -> 0.2.4 but did not regenerate the root package-lock.json, which still recorded the file: link at 0.2.3. The lock-sync drift guard (#2704/#3782) regenerates the root lock and fails on any residual diff, so the check went red. Regenerating updates exactly one line: the billion-context-pi-subagents version record 0.2.3 -> 0.2.4. Kernel lock verified clean (the PR does not touch kernel/).
The PR bumped kernel/package.json to 0.0.161 but neither lockfile was regenerated, leaving the root lock recording acp-kernel 0.0.159. The lock-sync gate (#2704/#3782) regens both locks and fails on any drift. This staleness already existed on master (kernel 0.0.160 vs root lock 0.0.159); the bump merely widened it. Pure version-line regen, no structural churn. Un-blocks the `test` lane.
The PR bumped kernel/package.json to 0.0.161 but neither lockfile was regenerated, leaving the root lock recording acp-kernel 0.0.159. The lock-sync gate (#2704/#3782) regens both locks and fails on any drift. This staleness already existed on master (kernel 0.0.160 vs root lock 0.0.159); the bump merely widened it. Pure version-line regen, no structural churn. Un-blocks the `test` lane.
The kernel-change commit bumped kernel/package.json 0.0.198 -> 0.0.199 but left both lockfiles at 0.0.198, so the #3782 lock-sync drift guard went red (and, like docs-sync, skipped the test matrix via the !failure() needs gate). Regenerated with npm install --package-lock-only (root + kernel); the diff is exactly the version line in each file.
) The lock-sync gate checks BOTH the root lockfile and the kernel's own package-lock.json (#3782 — the kernel keeps its standalone lockfile). The 0.0.198 → 0.0.199 bump must be mirrored in both. Two-line version sync in kernel/package-lock.json, no other churn.
…l 0.0.198 -> 0.0.199 bump (lock-sync diffs both lockfiles, #3782)
ai: zhipuai-lb/glm-5.3
kernel-change: lockfile sync only — kernel/package-lock.json 0.0.133 → 0.0.136 to match kernel/package.json(无 src 改动,无版本 bump)
一句话:#3767 的 0.0.136 bump 漏了重新生成 kernel/package-lock.json,锁停在 0.0.133。
npm ci会拒绝(锁不满足 package.json);与 [PR] protocol-stable core identity: same logical conversation, same ids in every dialect (#3642) #3658 时代修过的 C-H1 同型漂移npm install --package-lock-only重新生成,2 行 version 变更,无其他改动