Skip to content

release v0.1.167 - #1587

Merged
ranxianglei merged 2 commits into
masterfrom
2026-09-28_release-v0.1.167
Sep 28, 2026
Merged

ranxianglei merged 2 commits into
masterfrom
2026-09-28_release-v0.1.167

Conversation

@ranxianglei

@ranxianglei ranxianglei commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Step 1 of the post-merge checklist in #1582 ("Release 0.1.167 (routine)") — the routine patch after the advisory re-land; ships the new updater to the fleet so instances start polling billion-context-advisories.

Changes since v0.1.166

Two content changes (branch rebased onto current master 1facb6e7; diff vs master remains only the version bump):

Behavior changes (disclosed, intended): one background GET to the npm registry every ~3 min even when auto-update is off; additive advisory field in /__bili/status; no change to existing self-update behavior when no advisory matches; plus the #1549 wire-ordering edge case (content previously emitted after the finish frame now emits before/at it).

Pre-flight (local, rebased head 23800c99)

  • npm ci ✓ · npm run typecheck ✓ · npm test ✓ (3073 tests: 3061 pass / 0 fail / 12 e2e-gated skips) · npm run build ✓
  • CI runs the full gate + e2e matrix on this branch as well.

Note: the one-click fast path (Release (one-click)) would serve this routine patch equally well — if you prefer that route, close this PR and trigger the workflow instead (the drift guard makes both safe).

@github-actions

github-actions Bot commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-28_release-v0.1.167 (9ba2cff)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1524-pr.1587.73298b9

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

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 收到,开始按发版类 PR 规范审 #1587(release v0.1.167):PR 自身 diff 核对 + 版本区间回归审计(v0.1.166..HEAD)+ CI 状态确认。已发现一个需要处理的情况——分支切出后 master 又合入了 #1549(tag-tail drain fix),正在处理并重新验证,结论稍后回帖。

@ranxianglei
ranxianglei force-pushed the 2026-09-28_release-v0.1.167 branch from 2202dd2 to 23800c9 Compare September 28, 2026 11:48
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Review complete — mergeable. One fix applied directly on the branch during review (details below), everything re-verified on the new head.

Fix applied during review (stale base)

The branch was cut at e258bc80 (the #1582 re-land merge), but master moved on before this review: #1549 (fix(plugin): drain held tag tails before a terminal finish frame, fixes #1546) merged in after the cut. Merging as-is would have shipped #1549 inside v0.1.167 while the PR body claimed "exactly one content change" — an inaccurate changelog. Per §7.2 ("rebase to CURRENT master before claiming mergeable") I fixed it in place:

  • Rebased the single release v0.1.167 commit onto current master 1facb6e7 (clean, zero conflicts), force-pushed with lease: old head 2202dd2d → new head 23800c99.
  • Diff vs master remains exactly the isolated version bump (package.json + package-lock.json, 4 lines) — one-version-one-commit discipline intact, no content bundled.
  • Updated the PR body's "Changes since v0.1.166" to list both content changes and disclose fix(plugin): drain held tag tails before a terminal finish frame (#1546) #1549's behavior delta.

① Original issue (#1582 checklist step 1) — direction OK

Routine patch whose whole purpose is shipping the validated updater to the fleet so instances start polling billion-context-advisories. The updater-change discipline was followed end-to-end: #1483 reverted (#1580) → no-op 0.1.166 validated the existing path live (log evidence in #1582 OP) → re-land (#1582) → this release. Version math correct: 0.1.166 → 0.1.167 patch bump; npm latest still 0.1.166 = master's package.json version, so the one-click drift guard would pass too (both routes remain safe, per the note in the body). Duplicate screening: #1587 is the only open release PR — no racing release.

②b Version-window regression audit (v0.1.166..HEAD — 2 content changes)

A. Advisory watcher re-land (#1481/#1483 via #1582) — full audit already done in #1582 floor 3 against byte-identical content (git diff 1cc07c10 43dff1f7 = version lines only); I re-checked the touched-path ledger on this branch:

Existing behavior Verdict
Normal self-update loop Preserved — defers only while advisory active AND target resolvable (F2); manual bili update bypasses via force=true
Host-managed lanes (#991/#1196) Preserved — deferral branch still runs refreshDshProfileCopy; forceInstallVersion refuses pnpm-store/host-tree copies
Source-checkout guard (#580) Preserved — re-checked inside forceInstallVersion
Throttle/cross-process lock New .advisory-check throttle follows .update-check pattern; installs reuse the same lock + backup/verify/rollback chain
dist self-containment Kept — semver in tsup noExternal, exact pin; zod remains sole external dep

B. Tag-tail drain (#1546 via #1549) — went through its own full review cycle (two agent rounds + your deep review, verdict "merge as-is"). Window-audit re-check of its touched paths: ordinary streams byte-identical with no held tail (every return path reduces to pre-fix value); #463 frame-drop guards (hadTextOtherThanTextFields/googleFrameHasNonText) untouched so terminal frames always survive; fold accounting books into releasedMarkupChars like flushTails so degenerate-turn detection (#732/#821) semantics hold; tool-call arguments stay byte-exact (#1039). No additional regressions found.

④ Test validity & pre-flight (rebased head 23800c99)

  • Local: npm ci ✓ · typecheck ✓ · test ✓ (3073 tests: 3061 pass / 0 fail / 12 e2e-gated skips) · build ✓
  • CI on 23800c99: all green — full gate (ubuntu/windows × node 22/24) + entire e2e matrix (real codex/opencode/dsh/pi lanes vs deterministic fake upstream, hermetic registry e2e, codex overlay check) + version-guard + build-artifact: 17 success / 1 skipped / 0 fail.
  • The window's own regression suites carry teeth: 16 advisory tests incl. the verbatim F2 assertion (install untouched, cannotResolveTarget()=true, advisoryDeferring()=false, one warn per process); 11 finish-tail tests where stashing the fix turns 6 red (proven in fix(plugin): drain held tag tails before a terminal finish frame (#1546) #1549's thread).

⑤ Diff cleanliness

vs current master: ONLY package.json + package-lock.json version lines. Clean.

Behavior changes shipped in v0.1.167 (all intended, disclosed in PR body)

  1. Advisory watcher: one background GET to the npm registry every ~180s even when auto-update is off (off: BILI_ADVISORY_CHECK=0 / "advisoryCheck": false); additive advisory field in /__bili/status; self-update loop yields to an active resolvable-target advisory. Reason: critical-defect force-update channel (搞一个自动强制更新,针对重大bug的版本 #1481).
  2. fix(plugin): drain held tag tails before a terminal finish frame (#1546) #1549: content that previously emitted after the finish_reason/finishReason frame now emits before/at it — exactly the strict-consumer abort case (OpenCode 2.0.18); no other bytes change.
  3. (Non-blocking known gap, filed advisory 回滚形态公告:target↔latest 振荡(autoUpdate=ON)与回滚成功后无持久重启提示 #1588: rollback-shaped advisories can ping-pong for autoUpdate-on users and leave no persistent restart prompt post-rollback — only bites if such an advisory is ever published.)

Verdict

本版本引入回归:无。 可合并(人工 merge)。Merge 后按 #1582 清单继续 step 2/3 观察:空公告已就位(billion-context-advisories@0.0.2,npm 已确认),等一个 0.1.167 实例日志显示 watcher 命中且无动作即可。


中文摘要:审了 release v0.1.167——发现分支切出后 master 又合入了 #1549(tag-tail drain 修复),已在 PR 分支上直接 rebase 到当前 master(force-push 带 lease)、把 #1549 补进 changelog 并在 rebased head 重跑全套验证(本地 3061 过/0 挂 + CI 全绿含 e2e 矩阵);版本区间(v0.1.166 起)两项内容变更(advisory watcher 重落地、#1549)逐项回归审计均无回归,行为变更全部有意且已披露,可以合并。

@ranxianglei
ranxianglei merged commit d28bd18 into master Sep 28, 2026
18 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-28_release-v0.1.167 branch October 15, 2026 05:32
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