Repository navigation
fix(#1977): release-notes visibility surfaces only for critical-tier releases - #1983
Conversation
…releases Option C compromise: keep the #1870 watcher and surfaces, silent by default. New 'critical' tier is the only one that ever surfaces (CRITICAL UPDATE READY / CRITICAL UPDATE AVAILABLE); 'recommended' becomes record-only, and a pending restart alone no longer announces itself — only when the pending span carries a critical entry. - ReleaseTier += critical (parser + CI validator + docs) - getUpdateVisibility: visible = critical-in-span (#1977) - describeUpdateReady / acp_status wording: Critical update … - release-notes/package.json: re-tier inflated recommended -> routine (5 of 6 entries were 'recommended' — the nag #1977 complained about) - CONFIGURATION.md/.zh-CN, release-notes/README.md, reference/release.md: tier discipline documented Supersedes #1979 (full removal) per owner: 不能完全静默.
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.1999-pr.1983.a4b537aThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr1983.tgz
npm install -g packageInstall instructions are refreshed on each push. |
审查完成(分支 结构化七问
测试有效性
顺手小修(已推,标注 commit
|
Closes #1977 — the compromise variant ("不能完全静默"), supersedes #1979 (full removal — recommend closing that one in favor of this).
Problem
#1870 surfaces update notices on
acp_status+ the/acppanel by default, and the tier got inflated: 5 of 6 entries inrelease-notes/package.jsonarerecommended, so users see a nag nearly every release.Approach (Option C)
Keep the watcher and the surfaces, but silent by default: a new
criticaltier is the ONLY thing that ever surfaces.ReleaseTier += "critical"(parser, CI validator, docs)getUpdateVisibility:visible = span contains critical— routine/recommended never surface; a pending restart alone is silent too (it only speaks when the pending span carries a critical entry, because the restart matters then)describeUpdateReady/acp_statuswording →Critical update ready: … restart to finish./CRITICAL UPDATE READY (instance-level)/CRITICAL UPDATE AVAILABLE (instance-level)release-notes/package.json: re-tier the inflatedrecommendedentries →routine(none meet the critical bar; advisory-class defects went toadvisories/)critical= serious defect users must act on, below the advisory force-upgrade bar, used sparingly;recommended= record-only since Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #1977advisories/(搞一个自动强制更新,针对重大bug的版本 #1481) — entries here never trigger the safety chainVerification
npm run typecheckcleannode --import tsx --test tests/update-notes.test.ts— 6/6 pass (rewritten for Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #1977: recommended-only span invisible, pending restart without critical stays silent, critical surfaces with/without disk)Notes