Repository navigation
[PR] fix: sync the four plugin manifests to 0.1.207 on master - #4760
ranxianglei wants to merge 6 commits into
Conversation
master's package.json is 0.1.207 but all four plugin manifests were still 0.1.205, so scripts/sync-codex-plugin-version.mjs --check (the #4449 gate run by all three release workflows before tag/publish) exited 1 and any release branch cut from master was rejected. Run the sync script once on master; this commit carries its output — version field only in each manifest, no other changes.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6148-pr.4760.749b88dThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4760.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重:核心与在途 PR #4735 重复,但两者范围不同——#4760 干净,#4735 是捆绑了无关改动的超集。 同一件事(四个 manifest 0.1.205→0.1.207),当前有两个在途 PR:
建议:manifest 同步以 #4760 落地(干净且已验证);#4735 的 manifest 提交与 #4760 重复,其捆绑的存储/CRLF 改动应拆到各自正确范围的 PR 单独立项。是否关 #4735 由你定,我不代关。 结论先行:修法正确、最小、已本地实测验证,可合;唯一红是继承自 master 的既有测试红,与本 PR 的 4 行改动无因果。 八问:
本地实测(非「应该能过」):
CI:head 687a2bf 红的 5 个 shard(ubuntu 22/3、ubuntu 24/3、windows 22/3·4·5)全在 master 现有红集内 → 继承性失败,按总控走 #4599。需要的话我可以把 判定:本 PR 自身干净、正确、已验证,可合;合并前唯一前置是清掉继承自 master 的测试红(merge ci-fixes 或等 master 转绿)。重复项 #4735 请一并处置(建议保留 #4760、拆分/关闭 #4735,理由见上)。 |
(ai: vllm-qwen/qwen3.8-27b) CI 红 = 继承性失败(master 自身 born-red 簇),不是本 PR 引入。已按 #4599 协调协议把 ci-fixes 合入分支,等 CI 重跑。 核查过程
处置
八问结论
判定:等 CI 重跑结果;若个别分片仍红且签名落在在册簇内,归 #4599 由哨兵处理。 |
master window commits 293ae65/de5e03659 bumped kernel/package.json to 0.0.165 without regenerating the lockfiles; lock-sync re-resolution then rewrites the stale recorded versions (root 0.0.163, kernel 0.0.164) and fails. Pure recorded-version sync via npm install --package-lock-only; no dependency or semantic change.
Closes #4745
What
master's package.json is at 0.1.207 but all four plugin manifests (.agents/plugins/marketplace.json, .claude-plugin/marketplace.json, .claude-plugin/plugin.json, plugins/codex/.codex-plugin/plugin.json) were still at 0.1.205.
node scripts/sync-codex-plugin-version.mjs --checkexits 1, so every release workflow's pre-tag/publish #4449 gate would reject any release branch cut directly from master.Fix
Ran
node scripts/sync-codex-plugin-version.mjsonce on master; this commit carries its output. Diff is exactly 4 lines: the version field in each manifest, 0.1.205 → 0.1.207. package.json untouched (the version bump belongs to release branches only).Verification
--checkexit 1 with 4 drift lines (reproduced on bb7c249)--checkexit 0, all four OK at 0.1.207No config surface, no kernel, no wire changes.