Repository navigation
[PR] ci: fix two minor red gates on master (unused-exports + lock-sync) | ci: 修掉 master 上的两个小红门(unused-exports + lock-sync) - #4419
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5377-pr.4419.f068b08This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4419.tgz
npm install -g packageInstall instructions are refreshed on each push. |
…e passes #4434 (split-brain surface, merged at master tip) left three type exports with no cross-module consumers, red on pristine master. Drop the leading 'export' per the checker's INTERNAL_ONLY prescription — the types stay module-local. Complements in-flight #4419 (which covers the corrupt-index-child exports + lock-sync); different files, no overlap.
(ai: vllm-qwen/qwen3.8-27b) 来源:审 #4389(give-up 客户端事件带原因)时发现。 unused-exports 门在 master tip 上仍是红的,且失败签名已变——本 PR 的 diff 覆盖不到新出现的那部分:
接手本 PR 时建议:rebase 到当前 master 再合——corrupt-index-child 那组 hunk 依然有效;split-brain 那 3 个导出若不想与 #4389 重复处理,保持现状即可(两边改动不重叠,先后合入都不冲突)。若你更希望把全部门修复收拢到一个 PR,也可以把 b23c007 挪过来、在 #4389 撤掉,二选一都行。 |
(ai: vllm-qwen/qwen3.8-27b) 补一条(接上一条):master 红其实是第三个门—— |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.786-master.bc41fe4 # this exact build
npm install -g billion-context@master # always the newest merged build
|
什么问题
12:32 的 master CI run 39954118977 有两个静态门红了,测试腿本身全绿:
tests/corrupt-index-child.ts里 4 个导出(ENGPROOF_CHECK_NAMES、BANNER_CHECK_NAMES、CorruptIndexCheck、CorruptIndexVerdict)只在本文件内部使用,门要求删掉export关键字。父测试实际引用的是ENGPROOF_CHECKS/spawnCorruptIndexChild,不受影响。package-lock.json里嵌入的 workspace 版本还停在 0.0.159,门要求对齐(与 e733727 同型的一条同步提交)。怎么修
export(文件内使用照旧),本地node scripts/check-unused-exports.mjs→✓ unused-export gate: clean (6 waived)npm install --package-lock-only重新生成 lock → 只改 1 行(0.0.159 → 0.0.160)tests/storage-engine-proofs.test.ts全过影响面
纯红门修复,不改任何运行时行为;不依赖别的 PR。