Skip to content

[PR] fix: unblock master CI gates — regenerate stale config docs + drop orphaned export | 修复 master 红灯 CI 门禁(配置文档生成物过期 + 孤儿导出) - #3883

Closed
ranxianglei wants to merge 2 commits into
masterfrom
2026-10-20_master-ci-gates
Closed

ranxianglei wants to merge 2 commits into
masterfrom
2026-10-20_master-ci-gates

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Fixes #3881

What

Two required CI lanes are red on master itself (verified against base commit 39fb841d3 check-runs), so every open PR — including #3875 — sits at mergeable_state=blocked. Both failures pre-date any in-flight PR diff:

  1. docs-sync (the [docs][website] 配置文档单一事实源:从声明式 schema 生成 CONFIGURATION.md 与网站 /docs/(一步到位) #2107 drift guard): the committed CONFIGURATION.md / CONFIGURATION.zh-CN.md artifacts each carried two stale duplicate rows left behind when the website/config-reference/*.yaml seeds were updated for Storage wrap-up: 6 fixes + switch default mode to full (single PR) | 存储收尾六修 + 缺省模式翻 full(一个 PR 统一处理) #3818 (storage.unified default flip) and SQLite unified storage degraded to legacy-only (bili v0.1.201, node v20.19.5, win32-x64) #3788 (sqliteAutoDownload cooldown sentence). This PR re-runs node tools/gen-config-docs.mjs generate and commits the deterministic output (-2 duplicate rows per language; the current rows stay untouched).
  2. unused-exports: src/log-mask.ts: maskUrlForPublish flagged INTERNAL_ONLY — exported but only called by same-module maskUrlsForPublish (the [security][web] Diagnostics blob prints private relay hosts verbatim in the config section — the "secrets masked" header only masks values, not hosts | 诊断包 config 段原样输出内网中转地址:标题说"密钥已遮蔽",但只遮值不遮主机 #3811 publish-path usage consolidated into that wrapper). Drops the leading export; the function stays module-local and in use.

Behavior change

None. The docs lose only the duplicate stale rows; the export removal changes no runtime surface.

Config surface

None.

Verification

  • Local: node scripts/check-unused-exports.mjs → ✓ unused-export gate: clean (5 waived); re-running the docs generator after these commits produces zero further diff (idempotent).
  • Full-suite verdict = remote CI on this head.

Note: the branch was pushed via a fallback route after ordinary git push from the sandbox kept getting connection-reset; the pushed objects are byte-identical to the locally verified tree (local commits 957c26d12 + c5e4f7206).

awork added 2 commits October 20, 2026 06:03
The #2107 drift guard went red on master: the committed artifacts still carried two stale duplicate rows per file (the pre-#3818-flip 'storage.unified ... unset (shadow)' row and a pre-#3788 'storage.sqliteAutoDownload' row missing the 6-hour cooldown sentence), left behind when the yaml seeds were updated. Re-run tools/gen-config-docs.mjs generate and commit the deterministic output (-2 rows per file). No content change beyond removing the duplicates.
…#3881)

check-unused-exports flagged src/log-mask.ts: maskUrlForPublish as INTERNAL_ONLY: it is exported but only called by maskUrlsForPublish in the same module (the #3811 publish-path usage consolidated into that wrapper). Remove the leading 'export' so the gate passes without a waiver entry; behavior unchanged.
@ranxianglei ranxianglei changed the title fix: unblock master CI gates — regenerate stale config docs + drop orphaned export | 修复 master 红灯 CI 门禁(配置文档生成物过期 + 孤儿导出) [PR] fix: unblock master CI gates — regenerate stale config docs + drop orphaned export | 修复 master 红灯 CI 门禁(配置文档生成物过期 + 孤儿导出) Oct 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-20_master-ci-gates (c5e4f72)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.4595-pr.3883.ac02680

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

Option B — Download artifact

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

Install instructions are refreshed on each push.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

probe

1 participant