Skip to content

release v0.1.166 - #1578

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-28_release-v0.1.166
Sep 28, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-28_release-v0.1.166

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

No-op validation release for #1483

Version bump only — zero code changes (package.json + package-lock.json version fields).

Why: PR #1483 (advisory force-update) modifies src/update.ts, which is load-bearing for every future upgrade. Per AGENTS.md §5 (auto-update mechanism rule), the change must NOT ship until the existing upgrade path is proven healthy end-to-end on a no-op release:

  1. Merge this PR → CI publishes v0.1.166.
  2. Observe a real running install auto-updating 0.1.165 → 0.1.166 using the OLD updater code (log line ✔ billion-context auto-updated 0.1.165 → 0.1.166).
  3. Only then merge feat: force-update out of critical-defect versions via remote advisories #1483.

If step 2 fails, stop and investigate the existing path first — do not ship the updater change on top of an already-broken path.

Pre-flight (local, same gates as CI)

  • npm run typecheck — clean
  • npm test — 3046 tests, 3034 pass, 0 fail, 12 pre-existing gated skips
  • npm run build — OK, dist dep-free check passed

References #1483.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-28_release-v0.1.166 (99b8137)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1511-pr.1578.e0fd068

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-pr1578.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] 🏷 中文摘要:这是一次合规的 no-op 验证发布——PR 自身 diff 纯版本号、v0.1.165 以来窗口内除文档外零运行时变更(#1483 已干净回滚)、CI 全绿、npm 漂移守卫满足,可以合并(请人工合并)。

Release-window audit (auto-triggered per ②b: window expanded from PR diff to all changes since v0.1.165)

① Direction check — this is the AGENTS.md §5 no-op validation release required before shipping #1483 (updater change). History confirms the sequence is real: #1483 merged (6de711dc) then reverted via #1580 (44171bfa, branch revert-1483-until-noop). Correct order of operations.

② Regression audit of the full window v0.1.165..HEAD:

Item Verdict
PR's own diff vs current master Pure version bump: package.json 0.1.165→0.1.166 (1 line) + package-lock.json both version fields (2 lines). No dependency churn (zod stays 4.1.8).
PR base ancestry Base 1c60633c IS an ancestor of current master → merge result = master + version bump, no surprise content.
#1483 merge + #1580 revert Perfect revert, verified: git diff 6de711dc^ 44171bfa is empty — net-zero contribution to the tree.
#1522 / #1527 / #1564 (docs slimming) Docs-only: README rewrite, new CLIENTS.md/CLIENTS.zh-CN.md, TECHNICAL-NOTES*, SESSION-IDENTITY*, CONFIGURATION*, screenshots. No runtime effect.
Only src/ delta in window (src/server.ts) 2 comment-only lines (pointer README → TECHNICAL-NOTES.md, src/server.ts:2237 and src/server.ts:2734). Zero runtime code change.

本版本引入回归:无。 重大行为变更清单:无 — runtime code is byte-equivalent to v0.1.165; the tarball additionally carries the merged docs updates (non-runtime). Note for the record: "zero code changes" is exact for the PR's own diff; relative to published 0.1.165 the package also ships the docs-slimming that landed on master meanwhile — immaterial to the upgrade-path validation, which is what this release exists to prove.

Preconditions & gates:

  • npm latest = 0.1.165 = master's package.json → drift guard satisfied; 0.1.166 not yet published (404) ✓
  • Branch 2026-09-28_release-v0.1.166 + commit release v0.1.166 match the release.yml trigger patterns ✓
  • CI on head 99b81378: all checks success — full test matrix (ubuntu/windows × node 22/24), e2e suite, hermetic registry e2e, build-artifact, version-guard ✓

Verdict: mergeable. After merge, watch step 2 of the plan — a real install logging ✔ billion-context auto-updated 0.1.165 → 0.1.166 — before #1483 is re-applied. If that line never appears, stop and debug the existing path first.

@ranxianglei
ranxianglei merged commit 3bacfe0 into master Sep 28, 2026
18 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-28_release-v0.1.166 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