Skip to content

[PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master - #4524

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-24_rollout-seed-row
Oct 24, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-24_rollout-seed-row

Conversation

@ranxianglei

@ranxianglei ranxianglei commented Oct 24, 2026 •

Copy link
Copy Markdown
Owner

(ai: zai/glm-5.3)

Fixes #4520

这是啥问题?

#4505(插件车道服务端正史)合入后 master 每次 push、所有 PR 的 docs-sync/docs-coverage 全红——配置文档重生成漂移一行:rollout.features.pluginLaneServerHistory。

根因(挖到底)

功能的种子条目(website/config-reference/rollout.yaml)从未写入;CONFIGURATION.md 里那行是 #4491(ad98e7e)手改文档直接塞进去的,而且带着种子层被禁止的反引号(lint backtick forbidden in desc 自单源文档体系 #2107 引入即存在)。→ 该行从出生就不是生成器产物,种子→文档的单源链断了。功能本身完好(src/rollout.ts:78 percent:0,四处引用正常)。

改动(3 文件,+6/-4)

  1. rollout.yaml:rollout.features.base 之后补回条目(type boolean | number、默认 "0 (off)"、env BILI_ROLLOUT_PLUGIN_LANE_SERVER_HISTORY,描述与已提交文档同文、按 lint 去反引号);
  2. CONFIGURATION.md / .zh-CN.md:由生成器重写该行(唯一变化=去反引号)。

验证

本地 node tools/gen-config-docs.mjs generate → wrote 10 blocks / i18n ok,受控文件零额外漂移;即 CI 的 docs-sync(docs 全量再生成 diff)+docs-coverage 均通过的本地等价物。

范围外

不动任何 src/(功能已发)、不碰其他种子。合并后 master push CI 与积压 PR(#4519 carry 回执修复)的红道解除。

@github-actions

github-actions Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-24_rollout-seed-row (8daae67)

Latest build — install this exact version

npm install -g billion-context@0.0.5466-pr.4524.c33cad8

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
8daae67 billion-context@0.0.5466-pr.4524.c33cad8 build
c0b6335 billion-context@0.0.5458-pr.4524.87ba83d build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr4524.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei ranxianglei changed the title docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master [PR] docs: restore dropped pluginLaneServerHistory seed row — unblocks docs-sync on master Oct 24, 2026
@ranxianglei
ranxianglei force-pushed the 2026-10-24_rollout-seed-row branch from c0b6335 to 8daae67 Compare October 24, 2026 11:18
@ranxianglei
ranxianglei merged commit 8ae56a0 into master Oct 24, 2026
40 of 46 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.816-master.8ae56a0 (rolling master tag).

npm install -g billion-context@0.0.816-master.8ae56a0  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
docs-sync failed on this PR because master's generated CONFIGURATION.md block carried a hand-edited pluginLaneServerHistory row with no seed entry (root cause fixed on master by #4524, merged 8ae56a0). This empty commit recomputes the merge ref so CI re-evaluates the merge tree against the fixed master. Verified locally: generator reproduces all 4 watched files byte-exact on the new merge tree (393f4d1 + 8ae56a0); check-coverage ok.
ranxianglei added a commit that referenced this pull request Oct 24, 2026
… (throttle429 #4204, BILI_CODEX_STATE_MODE, #4524 zh punctuation) without regenerating CONFIGURATION.zh-CN.md, leaving docs-sync drifted for every PR
ranxianglei added a commit that referenced this pull request Oct 24, 2026
… (throttle429 #4204, BILI_CODEX_STATE_MODE, #4524 zh punctuation) without regenerating CONFIGURATION.zh-CN.md, leaving docs-sync drifted for every PR
antclt pushed a commit to antclt/billion-context that referenced this pull request Oct 25, 2026
… (throttle429 ranxianglei#4204, BILI_CODEX_STATE_MODE, ranxianglei#4524 zh punctuation) without regenerating CONFIGURATION.zh-CN.md, leaving docs-sync drifted for every PR
@github-actions github-actions Bot mentioned this pull request Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant