Skip to content

[PR] fix: unblock the two red master CI gates (unused-exports + docs-sync) | 修掉 master 上两个常红的 CI 门禁 - #3882

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

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

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Two independent sub-defects keep master CI red (found while working #3876). Same visible symptom — two gates fail on every PR — different mechanisms, managed as one checklist in the recorded issue.

1. unused-exports gate red since #3811.
src/log-mask.ts:121 exports maskUrlForPublish, but nothing outside that file consumes it (only use: src/log-mask.ts:137). Fixed per the gate's own instruction for the INTERNAL_ONLY case: drop the leading export. Grep confirms zero references in tests/, scripts/, kernel/, pi-subagents/.

2. docs-sync gate red (merge artifact).
CONFIGURATION.md and CONFIGURATION.zh-CN.md each carry two stale table rows sitting directly above their current versions: the pre-#3788 storage.sqliteAutoDownload row (missing the retry-cooldown sentence) and the pre-#3818 storage.unified row (still claiming the shadow default). The gate regenerates both files from the yaml seeds (tools/gen-config-docs.mjs generate) and diffs them against HEAD, so the fix is exactly the generator output: remove the four stale rows. Generator run verified idempotent (a second run produces zero diff).

Verification

  • node scripts/check-unused-exports.mjs -> clean on this head
  • node tools/gen-config-docs.mjs generate x2 -> idempotent on this head (the gate is generate + git diff --exit-code)
  • full-suite verdict = CI on this head

Behavior change

None at runtime: one internal-only export demoted (no external consumers exist), plus documentation dedup where the surviving rows are the current #3818/#3788 semantics.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-20_master-ci-gates-green (c522576)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.4594-pr.3882.e8e81f1

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-pr3882.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei ranxianglei changed the title fix: unblock the two red master CI gates (unused-exports + docs-sync) | 修掉 master 上两个常红的 CI 门禁 [PR] fix: unblock the two red master CI gates (unused-exports + docs-sync) | 修掉 master 上两个常红的 CI 门禁 Oct 19, 2026
@ranxianglei

Copy link
Copy Markdown
Owner Author

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

Closing: duplicate of #3871 (also #3877) — same symptom (two gates red on master: unused-exports + docs-sync), same mechanism, same root cause, byte-equivalent changeset (CONFIGURATION.md -2, CONFIGURATION.zh-CN.md -2, src/log-mask.ts +1/-1). First-come-first-served: #3871 opened 2026-10-19T17:43Z predates both, and its CI already shows docs-sync ✓ + unused-exports ✓ on head bdad5b0. My duplicate screening searched issues but not PRs, which is how this slipped through — closing mine.

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.

1 participant