Skip to content

[PR] fix: sync the four plugin manifests to 0.1.207 on master - #4760

Closed
ranxianglei wants to merge 6 commits into
masterfrom
2026-10-26_sync-plugin-manifests
Closed

ranxianglei wants to merge 6 commits into
masterfrom
2026-10-26_sync-plugin-manifests

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

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 --check exits 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.mjs once 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

  • Before: --check exit 1 with 4 drift lines (reproduced on bb7c249)
  • After: --check exit 0, all four OK at 0.1.207

No config surface, no kernel, no wire changes.

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.
@ranxianglei ranxianglei changed the title fix: sync the four plugin manifests to 0.1.207 on master [PR] fix: sync the four plugin manifests to 0.1.207 on master Oct 25, 2026
@github-actions

github-actions Bot commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-26_sync-plugin-manifests (0600111)

Latest build — install this exact version

npm install -g billion-context@0.0.6148-pr.4760.749b88d

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Recent builds (commit → version)

commit version build
0600111 billion-context@0.0.6148-pr.4760.749b88d build
9803721 billion-context@0.0.6063-pr.4760.75c9fd4 build
69a4144 billion-context@0.0.5952-pr.4760.4b5cbd8 build
11e2fd8 billion-context@0.0.5911-pr.4760.efbf117 build
687a2bf billion-context@0.0.5834-pr.4760.f6aa1a3 build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr4760.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

(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 行改动无因果。

八问:

  1. 是什么问题:master 上 package.json=0.1.207,四个插件 manifest 仍停在 0.1.205,node scripts/sync-codex-plugin-version.mjs --check 在 master 直接 exit 1。
  2. 什么原因导致的:发版流程只在 release 分支上单独跑一次同步脚本写回 manifest(reference/release.md step 3.5),master 本身不跑这步,manifest 版本因此没随 package.json 推进,累积落后两版(0.1.205 vs 0.1.207)。
  3. 影响范围与严重程度:p2。① master 的 --check 门禁常红;② Codex/Claude 市场按 manifest 声明版本判断「有无更新」,落后会让这两条车道在下次发版前看不到最新版本;③ 任何跳过 step 3.5 同步就从 master 切的 release 分支会在 release.yml:46 被拒。注:正常发版每版都会重跑同步覆盖,所以并非「所有从 master 切的 release 必被拒」——原 issue 措辞略强,但底层漂移属实、值得修。不涉及用户数据/缓存。
  4. 怎么修复的:在 master 上跑一次同步脚本,把 package.json 唯一真值写回四个 manifest,作为本提交;不动 package.json(版本号只在 release 分支动,合规)。
  5. 是否有回归问题:无。纯 4 文件各 1 行版本号元数据,不碰 kernel/wire/config/持久化;脚本逻辑确认只改这四处,且 Claude marketplace 顶层 schema 级 "version":"1" 未被误碰,idempotent 无副作用。CI 上红的 5 个 test shard 是继承自 master(bb7c24972 同批 shard 本就红,见 CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599),与 4 行字符串改动无关。
  6. 是否破坏缓存:不涉及(无任何缓存/重试/游标/去重键路径被触碰)。
  7. 是否改了设计方向:不涉及。
  8. 是否引入新配置:不涉及。

本地实测(非「应该能过」):

  • before(master bb7c249):--check exit 1,恰好 4 条漂移行。
  • after(PR head 687a2bf):--check exit 0,四文件全部 OK … 已是 0.1.207。
  • release.yml:37-46 确有该门禁(is_release==true 时跑 --check),影响面成立。

CI:head 687a2bf 红的 5 个 shard(ubuntu 22/3、ubuntu 24/3、windows 22/3·4·5)全在 master 现有红集内 → 继承性失败,按总控走 #4599。需要的话我可以把 origin/ci-fixes(tip 1fa9373)merge 进本 PR 分支清掉继承红再重触发——你点头我就推。

判定:本 PR 自身干净、正确、已验证,可合;合并前唯一前置是清掉继承自 master 的测试红(merge ci-fixes 或等 master 转绿)。重复项 #4735 请一并处置(建议保留 #4760、拆分/关闭 #4735,理由见上)。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

CI 红 = 继承性失败(master 自身 born-red 簇),不是本 PR 引入。已按 #4599 协调协议把 ci-fixes 合入分支,等 CI 重跑。

核查过程

处置

八问结论

  1. 是什么问题:本 PR 的 CI test 分片红(10 个分片中 5 个)。
  2. 什么原因导致的:master(bb7c249)自带多组 born-red 测试簇(storage restamp 相关、golden 未 re-pin、opencode-inline 断言错位等,详见 CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599 登记);本 PR 基于该 base,继承其红。根因在 master 侧,不在本 PR 代码。
  3. 影响范围与严重程度:仅影响本 PR 的 CI 门禁、阻塞合并;对外部用户零影响(内容是 4 行 marketplace manifest 版本号)。
  4. 怎么修复的:按 CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599 协议 merge 哨兵收敛分支 origin/ci-fixes 进 PR 分支——master 级修复收敛在 ci-fixes 上,不在本分支重复修。
  5. 是否有回归问题:无。既有行为审计:本 PR 自身改动仅 4 个 manifest 版本字段(marketplace 更新探测依赖该值,0.1.205→0.1.207 对齐 package.json,正是本 PR 的预期行为);merge 带入的 13 个文件(persist remap、blog CRLF、tests/goldens)已由哨兵在多个其他 PR 上收敛过,本分支未在其之上新增语义。
  6. 是否破坏缓存:不涉及(无运行时路径或缓存策略变更)。
  7. 是否改了设计方向:否。
  8. 是否引入了新的配置:否。

判定:等 CI 重跑结果;若个别分片仍红且签名落在在册簇内,归 #4599 由哨兵处理。

ci-check added 4 commits October 26, 2026 10:15
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[release] master fails the #4449 manifest gate: all four plugin manifests stuck at 0.1.205

1 participant