Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions .github/workflows/release-notes.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,10 @@ name: Publish Release Notes
# Doc shape (schema 1):
# releases: newest-first; ≤20 entries (consumers cap the same way);
# fields: version (exact tag), date (YYYY-MM-DD), tier, summary.
# tier: "routine" (default) | "recommended" (worth restarting soon).
# Critical defects stay in advisories/ (#1481) — this doc never claims
# critical.
# tier: "routine" (default) | "recommended" (restart-soon, record-only)
# | "critical" (serious defect users must act on — the only tier
# users ever see, #1977). Force-upgradeable defects stay in
# advisories/ (#1481) — entries here never trigger the safety chain.

on:
push:
Expand Down Expand Up @@ -60,8 +61,8 @@ jobs:
process.exit(1);
}
seen.add(e.version);
if (e.tier !== 'routine' && e.tier !== 'recommended') {
console.error(e.version, ': tier must be routine|recommended, got', JSON.stringify(e.tier));
if (e.tier !== 'routine' && e.tier !== 'recommended' && e.tier !== 'critical') {
console.error(e.version, ': tier must be routine|recommended|critical, got', JSON.stringify(e.tier));
process.exit(1);
}
if (typeof e.summary !== 'string' || !e.summary.trim()) {
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ jobs:
- name: Verify release-notes entry (#1870)
# Visibility gate: every stable release must carry a tiered,
# user-meaningful entry in release-notes/package.json (the entry is
# part of the release prep PR, model-written, tier routine|recommended).
# part of the release prep PR, model-written, tier routine|recommended|critical).
# Fails BEFORE tagging/publishing so nothing ships invisible.
if: steps.check.outputs.is_release == 'true' && steps.pre.outputs.prerelease == 'false'
run: |
Expand Down
2 changes: 1 addition & 1 deletion CONFIGURATION.md
Original file line number Diff line number Diff line change
Expand Up @@ -809,7 +809,7 @@ Environment variables take precedence over the config file. They are useful for
| `BILI_MODEL_INFO_RETRY_MS` | Cooldown (ms) before the dsh native plugin re-resolves the current model's context window after a resolve that failed or returned no window (#1812/#1836): a cached entry without a window is not final — instead of latching headerless for the process lifetime, the next request after this cooldown triggers a retry. Default `30000`; non-numeric or negative values fall back to `30000`. Test hook — shortened by the dsh-native unit test so it never waits wall-clock; leave unset in production. |
| `BILI_ADVISORY_CHECK` | Set to `0` to disable the critical-defect advisory watcher (#1481). Default ON — it runs independently of `ACP_AUTO_UPDATE` so that installs with auto-update off still get force-updated out of a known-broken version range. Fail-open: an unreachable/malformed source only warns, never blocks model traffic. File-config key: `advisoryCheck`. |
| `BILI_ADVISORY_URL` | Override for the advisory document URL. Default: the companion package `billion-context-advisories` on the configured registry (`BILI_UPDATE_REGISTRY` aware). File-config key: `advisoryUrl`. |
| `BILI_RELEASE_NOTES_CHECK` | Set to `0` to disable the tiered release-notes visibility watcher (#1870). Default ON — pure visibility: fetches the companion release-notes doc and surfaces "update ready — restart to finish" (disk newer than running) or "recommended update available" on `acp_status` and the `/acp` panel. Never installs, never restarts; fail-open. File-config key: `releaseNotesCheck`. |
| `BILI_RELEASE_NOTES_CHECK` | Set to `0` to disable the release-notes visibility watcher (#1870). Default ON — pure visibility, silent by default (#1977): fetches the companion release-notes doc and surfaces "CRITICAL update ready — restart to finish" (disk newer than running) or "critical update available" on `acp_status` and the `/acp` panel ONLY when the pending span contains a `critical`-tier entry; routine/recommended releases never surface. Never installs, never restarts; fail-open. File-config key: `releaseNotesCheck`. |
| `BILI_RELEASE_NOTES_URL` | Override for the release-notes document URL. Default: the companion package `billion-context-release-notes` on the configured registry (`BILI_UPDATE_REGISTRY` aware). File-config key: `releaseNotesUrl`. |
| ~~`BILI_HOST_USAGE_CREDIT`~~ / ~~`hostUsageCredit`~~ | **Removed in #660.** Used to select the host-facing usage mode. The #408 uncompressed-baseline backfill is gone entirely — every host now reports the actually-forwarded (post-fold) request as provider-measured (matches `[acp-usage] input=`). Old values left in env or the config file are ignored; remove them. See the "Bug history lesson" section of PR #691. |
| `ACP_PROVIDERS` | Path to an external `providers.json` (legacy / shared file). |
Expand Down
2 changes: 1 addition & 1 deletion CONFIGURATION.zh-CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -808,7 +808,7 @@
| `BILI_MODEL_INFO_RETRY_MS` | dsh 原生模型窗口解析失败(或解析结果不带窗口)后的重试冷却(毫秒,#1812/#1836):匹配的缓存条目没有 context window 时不视为最终结果 —— 不再让整个进程生命周期 latching 成无 header 状态,而是该冷却过期后由下一个请求触发重新解析。默认 `30000`;非数字或负值回退 `30000`。测试钩子 —— dsh-native 单元测试用它缩短冷却、避免真实等待;生产环境保持 unset。 |
| `BILI_ADVISORY_CHECK` | 设为 `0` 禁用严重缺陷公告监视器(#1481)。默认开启 —— 它独立于 `ACP_AUTO_UPDATE` 运行,确保关闭了自动更新的安装也能被强制移出已知缺陷版本范围。fail-open:公告源不可达/格式错误只告警,绝不阻断模型流量。文件配置键:`advisoryCheck`。 |
| `BILI_ADVISORY_URL` | 公告文档 URL 覆盖。默认:已配置 registry(感知 `BILI_UPDATE_REGISTRY`)上的伴生包 `billion-context-advisories`。文件配置键:`advisoryUrl`。 |
| `BILI_RELEASE_NOTES_CHECK` | 设为 `0` 禁用分级发版说明可见性监视器(#1870)。默认开启 —— 纯可见性:拉取伴生发版说明文档,并在 `acp_status` 与 `/acp` 面板提示「更新已就绪待重启」(磁盘版本新于运行版本)或「存在推荐更新」。绝不安装、绝不重启;fail-open。文件配置键:`releaseNotesCheck`。 |
| `BILI_RELEASE_NOTES_CHECK` | 设为 `0` 禁用发版说明可见性监视器(#1870)。默认开启 —— 纯可见性,且默认静默(#1977):拉取伴生发版说明文档,仅当待更新跨度内含 `critical` 级条目时,才在 `acp_status` 与 `/acp` 面板提示「CRITICAL 更新已就绪待重启」(磁盘版本新于运行版本)或「存在 critical 更新」;routine/recommended 级发版永不上屏。绝不安装、绝不重启;fail-open。文件配置键:`releaseNotesCheck`。 |
| `BILI_RELEASE_NOTES_URL` | 发版说明文档 URL 覆盖。默认:已配置 registry(感知 `BILI_UPDATE_REGISTRY`)上的伴生包 `billion-context-release-notes`。文件配置键:`releaseNotesUrl`。 |
| ~~`BILI_HOST_USAGE_CREDIT`~~ / ~~`hostUsageCredit`~~ | **#660 已移除。** 曾用于选择宿主可见的用量模式。#408 的未折叠基线回补(backfill)已整体删除 —— 所有宿主现在统一上报“实际转发(后折叠)请求”的 provider 实测用量,与 `[acp-usage] input=` 一致。遗留该环境变量 / 配置键的旧值会被忽略,请删除。教训详见 PR #691 的 “Bug 历史教训” 一节。 |
| `ACP_PROVIDERS` | 指向外部 `providers.json` 的路径(旧版 / 共享文件)。 |
Expand Down
9 changes: 6 additions & 3 deletions reference/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,9 +43,12 @@ The Agent does steps 1–6, the human does step 7 (merge).
"summary": "what changes FOR THE USER, one line, issue/PR refs"
}
```
- `tier`: `routine` (default) or `recommended` (worth restarting soon —
correctness/cache/self-heal fixes; marketing is NEVER recommended).
Critical defects go to `advisories/`, never here.
- `tier`: `routine` (default) | `recommended` (restart-soon record —
correctness/cache/self-heal fixes; NOT user-visible, marketing is NEVER
recommended) | `critical` (a serious defect users must act on — the only
tier that ever surfaces to users, #1977; use sparingly, when the fix
matters more than the silence). Force-upgradeable defects go to
`advisories/`, never here.
- The summary is model-written, ≤400 chars, newest-first order, cap 20
entries. NEVER hand-edit the companion package's own `"version"` field —
CI bumps it on publish.
Expand Down
29 changes: 21 additions & 8 deletions release-notes/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,10 @@

Tiered, model-written release notes consumed by the proxy's visibility
watcher (`src/update-notes.ts`): acp_status and the `/acp` panel use them to
tell users and agents "an update is ready — restart to finish" or "a
recommended release exists", with a per-release summary and the user-side
span (everything between the running version and the newest release).
tell users and agents "a critical update is ready — restart to finish" or
"a critical fix is available" — ONLY for `critical`-tier entries (#1977:
silent by default) — with a per-release summary and the user-side span
(everything between the running version and the newest release).

Companion package mechanics mirror `advisories/` (#1481):

Expand All @@ -21,19 +22,31 @@ Companion package mechanics mirror `advisories/` (#1481):
|----------|----------|----------------------------------------------------|
| version | yes | Exact released version (semver) |
| date | no | `YYYY-MM-DD` release date |
| tier | yes | `routine` (default) or `recommended` (restart soon)|
| tier | yes | `routine` (default) / `recommended` (restart soon, record-only) / `critical` (see below) |
| summary | yes | One user-meaningful line, ≤400 chars, model-written|

Rules: newest-first, ≤20 entries, no duplicates. `recommended` is for
"worth restarting soon" (correctness/cache fixes, self-heal fixes) — NOT for
marketing. Critical defects stay in `advisories/` — this doc never claims
critical.
Rules: newest-first, ≤20 entries, no duplicates. Tier discipline (#1977):

- `routine` — default. The overwhelming majority of releases.
- `recommended` — "worth restarting soon" (correctness/cache fixes,
self-heal fixes); RECORD-ONLY since #1977: it feeds the release log but
never surfaces to users. NOT for marketing.
- `critical` — the release fixes a serious defect users must act on
(correctness / data / billing class) that sits BELOW the advisory bar.
The only tier that surfaces (`CRITICAL UPDATE READY/AVAILABLE` on
acp_status + the `/acp` panel). Use sparingly and deliberately — a
nag-per-release here is exactly what #1977 fixed.

Force-upgradeable critical defects stay in `advisories/` (#1481) — entries
here never trigger the safety chain, they only make an update visible.

## Release process (enforced by gates)

1. **Prep:** as part of the release prep, add the new version's entry to
`release-notes/package.json` (tier + summary). The summary is
model-written: describe what changes FOR THE USER, cite issue/PR numbers.
Pick the tier per the discipline above — `critical` only for serious
defect fixes users must act on; when in doubt, `routine`.
2. Merge to master. The publish workflow ships the updated doc.
3. Dispatch the one-click release (or merge the release PR).
`release-manual.yml` checks the entry at dispatch time; `release.yml`
Expand Down
10 changes: 5 additions & 5 deletions release-notes/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -14,25 +14,25 @@
{
"version": "0.1.181",
"date": "2026-10-03",
"tier": "recommended",
"tier": "routine",
"summary": "Window & preflight accuracy wave: dsh context windows resolve again after every resolveModelInfo call failed on a detached receiver (#1943); preflight no longer fires at 59–63% real usage — local estimates are now calibrated against provider-reported usage (#1940, #1933); pi virtual-model selections no longer double-compress (#1962); re-signed SDK-HMAC-SHA256 egress on armed tunnels (#1884)."
},
{
"version": "0.1.180",
"date": "2026-10-02",
"tier": "recommended",
"tier": "routine",
"summary": "OpenCode WebSocket traffic is intercepted again — compression and usage stats no longer silently no-op on OpenCode ≥ 2.0.20 (#1844)."
},
{
"version": "0.1.179",
"date": "2026-10-01",
"tier": "recommended",
"tier": "routine",
"summary": "Compression is now inherited across agent restart / resume / new-branch forks (#1834): folded summaries survive instead of silently re-expanding on the wire (claude-code and openai-chat wires; codex/gemini in #1853 follow-up)."
},
{
"version": "0.1.178",
"date": "2026-10-01",
"tier": "recommended",
"tier": "routine",
"summary": "dsh installs self-heal: profile bundles now converge to the global version automatically (#1803/#1804) — fixes the one-time 'invalid plugin' boot crash after a new bili publish."
},
{
Expand All @@ -44,7 +44,7 @@
{
"version": "0.1.176",
"date": "2026-10-01",
"tier": "recommended",
"tier": "routine",
"summary": "Stability wave: zero-injection session identity keeps the prefix cache hot across fork/resume (#1692/#1611); launcher port hardening (#1756); ACP tag-echo strip no longer eats prose (#1722); responses degenerate-output guard and transport replay retry."
}
]
Expand Down
17 changes: 10 additions & 7 deletions src/acp-status.ts
Original file line number Diff line number Diff line change
Expand Up @@ -150,17 +150,20 @@ export function handleAcpStatus(args: Record<string, unknown>, ctx: AcpStatusCtx
}
const upd = getUpdateVisibility(VERSION);
if (upd.visible) {
// #1870: the self-updater is a silent courier on native lanes — the
// "Restart to finish" log line never reaches pi/opencode/dsh users,
// so disk runs new while the process runs old. This is the surface
// agents actually poll: tell them a restart is actionable NOW, or
// that a recommended release exists when auto-update is off.
// #1870 + #1977: the self-updater is a silent courier on native
// lanes — the "Restart to finish" log line never reaches
// pi/opencode/dsh users, so disk runs new while the process runs old.
// This is the surface agents actually poll — but by default it is
// SILENT (#1977: not every release deserves the user's attention);
// it only speaks when the span carries a critical-tier entry,
// telling them a restart is actionable NOW, or that a critical fix
// exists while auto-update is off.
extra.push("");
const lines: string[] = [];
if (upd.pendingRestart) {
lines.push(`UPDATE READY (instance-level): ${upd.diskVersion} downloaded — restart this agent's proxy to finish (running ${upd.runningVersion}).`);
lines.push(`CRITICAL UPDATE READY (instance-level): ${upd.diskVersion} downloaded — restart this agent's proxy to finish (running ${upd.runningVersion}).`);
} else {
lines.push(`UPDATE AVAILABLE (instance-level): newer recommended release on the channel — running ${upd.runningVersion}.`);
lines.push(`CRITICAL UPDATE AVAILABLE (instance-level): release with a critical-tier fix on the channel — running ${upd.runningVersion}.`);
}
for (const e of upd.span) {
lines.push(` · ${e.version} [${e.tier}] ${e.summary}`);
Expand Down
8 changes: 4 additions & 4 deletions src/cli.ts
Original file line number Diff line number Diff line change
Expand Up @@ -631,10 +631,10 @@ export async function main(): Promise<void> {
}),
});
}
// #1870: tiered release-notes visibility — fetch + cache only (never
// installs, never restarts). Runs independently of autoUpdate for the
// same reason as the advisory watcher: installs with auto-update off
// still deserve to learn a recommended update exists.
// #1870 release-notes visibility (#1977 silent by default) — fetch +
// cache only (never installs, never restarts). Runs independently of
// autoUpdate for the same reason as the advisory watcher: installs with
// auto-update off still deserve to learn when a critical-tier fix exists.
if (opts.releaseNotesCheck) {
startReleaseNotesWatcher({
packageName: PACKAGE_NAME,
Expand Down
7 changes: 4 additions & 3 deletions src/plugin.ts
Original file line number Diff line number Diff line change
Expand Up @@ -868,9 +868,10 @@ export function handlePluginStatus(conversationId: string, res: import("node:htt
}
const upd = getUpdateVisibility(VERSION);
if (upd.visible) {
// #1870: visibility for the silent courier — one line, same
// before-footer slot as the advisory (remote-doc text; the $-escape
// below already covers it).
// #1870 visibility for the silent courier, #1977 display policy:
// silent unless the span carries a critical-tier entry — one line,
// same before-footer slot as the advisory (remote-doc text; the
// $-escape below already covers it).
preFooter.push(describeUpdateReady(upd));
}
const webUrl = webSessionUrl(deps.webOrigin, session.id);
Expand Down
Loading
Loading