Skip to content

fix: sync package-lock kernel version metadata to 0.0.115 (unblock lock-sync gate) - #2717

Closed
ranxianglei wants to merge 2 commits into
masterfrom
2026-10-11_lock-kernel-metadata-sync
Closed

ranxianglei wants to merge 2 commits into
masterfrom
2026-10-11_lock-kernel-metadata-sync

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Closes #2716

One-line lockfile sync: packages["kernel"] version 0.0.114 -> 0.0.115, exactly what npm install --package-lock-only regenerates on the current tree (verified locally: no other line changes; matches the drift blob in the failing CI job logs, 768b34bd9 -> 43841d478).

Why this is safe and not a content change

Unblocks

Every open PR is currently mergeable_state: blocked with all test legs skipped because test needs the guard tier incl. lock-sync (e.g. #2713, which otherwise passes review). Merging this restores the full test gate for all PRs.

@github-actions

github-actions Bot commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-11_lock-kernel-metadata-sync (b6a0866)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.2940-pr.2717.8fa99e7

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-pr2717.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 #2717(拉分支 → 逐提交比对 → 查 CI)。结论:该 PR 已被 master 上的等价提交取代,相对 master 净 diff 为空,建议关闭而非合并。

核查事实

  • PR 唯一改动:package-lock.json 中 packages["kernel"] 版本 0.0.114 → 0.0.115,blob 过渡 768b34bd9 → 43841d478(与 issue 正文引用的 drift blob 完全一致)。
  • 同一改动已由 owner 于 Oct 11 09:06(+08:00)直接落到 master:commit 67c811e3c「chore: sync package-lock kernel entry to 0.0.115 (lock-sync guard)」,author ranxianglei,blob 过渡同为 768b34bd9 → 43841d478 —— 与本 PR 的 agent commit 26ea466a2(Oct 11 09:19,+08:00)逐字节相同。
  • 随后 master 被 merge 回本分支(当前 tip b6a0866af),把 owner 那条已落地的修复带进来,于是 PR head 相对 master 的净 diff 为空(mergeable=True,无冲突)。
  • 当前 master 记录的 kernel 版本已是 0.0.115;master 的 lock-sync check = success(绿)。即 lock-sync gate red on master: package-lock records acp-kernel 0.0.114 while tree has 0.0.115 — every PR blocked, test legs skipped #2716 那个把全体 PR 卡在 guard tier 的问题,master 侧已经解决。
  • 本 PR head 的 lock-sync 也 = success;此刻 mergeable_state: blocked 仅因 4 条 test 矩阵腿还在 in_progress(排队中,非失败、非冲突)。

结构化八问

  1. 是什么问题:package-lock 记录的 in-repo file: devDependency acp-kernel 版本(0.0.114)落后于 kernel/package.json(0.0.115,自 [Bug][proxy] unframed host-side history deletion leaves zombie fold blocks rendering carriers forever — one carrier flaps in/out every turn (persistent prefix-cache churn) #2695 起的合法内核变更),触发 fix: sync package-lock.json version metadata + add lock-sync CI guard #2711 新增的 lock-sync 门禁红。
  2. 什么原因导致:内核源码合法 bump 到 0.0.115 后 lockfile 未同步;fix: sync package-lock.json version metadata + add lock-sync CI guard #2711 的 lock-sync sync 跑在早于 3956f57 的树上,记成了 0.0.114。
  3. 影响范围与严重程度:纯元数据一行,无运行期行为;曾使所有 open PR 的 test 腿被 guard tier 卡住。严重度=内部 CI 阻塞、无外部用户影响;现已解除(master 已修)。
  4. 怎么修复的:一行把 lockfile 的 kernel 版本对齐到 0.0.115。但该修复已由 owner 的 67c811e3c 先行落到 master,故本 PR 退化为净空操作。
  5. 是否有回归:不涉及。无源码/配置/依赖/时序/输出格式变化;合并本 PR 不会改变 master 任何字节。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及。
  8. 是否引入新配置:不涉及。

处置建议

  • 关闭 fix: sync package-lock kernel version metadata to 0.0.115 (unblock lock-sync gate) #2717(superseded / duplicate),指向已落地的 67c811e3c;不要合并(合并是净空操作,只会多一条冗余 merge)。
  • 我未做任何合并/关闭动作(合并为 human-only 规则);如需我代为关闭或补打 重复/superseded 标签,说一声即可。
  • 其余曾被卡的 PR 对 lock-sync 的依赖已在 master 满足,它们会在各自 test 腿跑完后正常放行,无需额外操作。

@ranxianglei

Copy link
Copy Markdown
Owner Author

This PR's single change (lock packages["kernel"] 0.0.114 → 0.0.115) already landed on master out-of-band: commit 67c811e (2026-10-11 09:06 +0800) rode into master through the #2710 merge 5b65b65 (09:24:31 +0800). After master was merged into this branch (b6a0866), the diff vs master is zero — latest evaluation is all-green incl. lock-sync, and local regeneration on the master tip reproduces the committed lock byte-for-byte (blob 43841d478…, matching the value predicted in #2716).

Nothing left to review or merge here, so closing as redundant. If you'd rather keep this as the formal vehicle for Closes #2716, reopen and merge (it's a no-op); otherwise close #2716 directly — it is verified fixed.

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.

lock-sync gate red on master: package-lock records acp-kernel 0.0.114 while tree has 0.0.115 — every PR blocked, test legs skipped

1 participant