Repository navigation
[PR] fix: repair red CI guards on master (unused-exports + docs-sync) - #3877
Closed
ranxianglei wants to merge 2 commits into
Closed
ranxianglei wants to merge 2 commits into
ranxianglei wants to merge 2 commits into
Conversation
added 2 commits
October 20, 2026 05:11
…d-exports gate (#3811 follow-up)
…ft by recent merges
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4590-pr.3877.cc0cb05This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3877.tgz
npm install -g packageInstall instructions are refreshed on each push. |
This was referenced Oct 19, 2026
Closed
Owner
Author
|
(ai: vllm-qwen/qwen3.8-27b) Closing: duplicate of #3871 — same symptom/mechanism/root cause, byte-equivalent changeset (CONFIGURATION.md -2, CONFIGURATION.zh-CN.md -2, src/log-mask.ts +1/-1), same base 39fb841. First-come-first-served: #3871 (opened 2026-10-19T17:43Z) predates this one (21:12Z), and its CI already shows docs-sync ✓ + unused-exports ✓ on head bdad5b0. |
This was referenced Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
Two tier-1 guard jobs fail on master itself (reproduced locally on pristine master
39fb841d3, before any PR content):unused-exportsflagssrc/log-mask.ts:maskUrlForPublishis exported but has zero external importers — it is only called internally bymaskUrlsForPublish(same file). Theexportwas introduced by [security][web] Diagnostics blob prints private relay hosts verbatim in the config section — the "secrets masked" header only masks values, not hosts | 诊断包 config 段原样输出内网中转地址:标题说"密钥已遮蔽",但只遮值不遮主机 #3811 (fix: mask private endpoint hosts in the publish-boundary diagnostics blob).docs-syncfails because the committedCONFIGURATION.md/CONFIGURATION.zh-CN.mdcontain stale duplicated rows the generator no longer emits: an oldstorage.unifiedrow (pre-Storage wrap-up: 6 fixes + switch default mode to full (single PR) | 存储收尾六修 + 缺省模式翻 full(一个 PR 统一处理) #3818 default flip) sitting next to the current one, and an oldstorage.sqliteAutoDownloadrow missing the SQLite unified storage degraded to legacy-only (bili v0.1.201, node v20.19.5, win32-x64) #3788 cooldown sentence — merge-resolution residue from recent storage merges.Why it matters
.github/workflows/ci.ymlgatesstatic-gatesand the fulltestmatrix behind!failure()of the earlier jobs, so these two red guards make every PR's merge-ref run skip its entire test suite — no PR can get a full-suite verdict while master carries them. This is what blocked the test lanes of #3867.Changes (5 lines across 3 files)
src/log-mask.ts: drop theexportkeyword frommaskUrlForPublish(one word; no importers anywhere in src/, tests/, scripts/, tools/).CONFIGURATION.md/CONFIGURATION.zh-CN.md: commit the output ofnode tools/gen-config-docs.mjs generate(4 deletions total — only the stale duplicate rows; no key added, renamed or re-semanticed, so no config-surface change).Verification
node scripts/check-unused-exports.mjs→ clean (5 waived);npm run typecheck→ clean;git statusafter regeneration → exactly the two doc files, deletions only.Discovered during review of #3867 (its CI showed both guards failing on the merge ref while passing on the bare head).