Repository navigation
fix: sync package-lock kernel version metadata to 0.0.115 (unblock lock-sync gate) - #2717
ranxianglei wants to merge 2 commits into
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2940-pr.2717.8fa99e7This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2717.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 已核对 PR #2717(拉分支 → 逐提交比对 → 查 CI)。结论:该 PR 已被 master 上的等价提交取代,相对 master 净 diff 为空,建议关闭而非合并。 核查事实
结构化八问
处置建议
|
|
This PR's single change (lock Nothing left to review or merge here, so closing as redundant. If you'd rather keep this as the formal vehicle for |
Closes #2716
One-line lockfile sync:
packages["kernel"]version 0.0.114 -> 0.0.115, exactly whatnpm install --package-lock-onlyregenerates 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
file:devDependencyacp-kernel, which already says 0.0.115 inkernel/package.jsonsince 3956f57 ([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, a legitimate kernel/src change with its mandated bump).lock-syncgate added by fix: sync package-lock.json version metadata + add lock-sync CI guard #2711, whose own sync ran against a tree predating 3956f57 and recorded 0.0.114.Unblocks
Every open PR is currently
mergeable_state: blockedwith alltestlegs skipped becausetestneeds the guard tier incl.lock-sync(e.g. #2713, which otherwise passes review). Merging this restores the full test gate for all PRs.