Skip to content

release v0.1.178 - #1810

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-01_release-v0.1.178
Oct 1, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-01_release-v0.1.178

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.

Changes since v0.1.177

@ranxianglei
ranxianglei merged commit b764faf into master Oct 1, 2026
18 checks passed
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-10-01_release-v0.1.178 (a3815bf)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1785-pr.1810.2bd9a00-a2

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

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 收到。这是 one-click release 的自动 fallback PR(直推 master 被 branch protection 拦下),带 ework-agent-pr 标记——按规则不重做,做版本区间回归审计。核验时 PR 已于 02:30:02Z 合并;以下为完整结论。

状态核验(全部实测)

  • PR release v0.1.178 #1810:已合并(b764faf5);CI 全绿——test ubuntu/windows × 22/24 四矩阵、codex e2e、release job 全部 success(version-guard skipped 为常态)。
  • Release commit a3815bf1:逐行核对,仅 package.json + package-lock.json 的版本行 0.1.177→0.1.178,无夹带 ✓(符合 §4/§5 one-version-one-commit)。
  • Tag v0.1.178 已建;npm view billion-context version = 0.1.178(latest 已生效)。发布闭环完成。

版本区间审计(v0.1.177..v0.1.178):窗口内仅一个内容提交 da65538b(PR #1804,#1803 的修复),整体审阅如下:


结构化七问

  1. 是什么问题:不是缺陷,是版本发布 PR——one-click 直推被 branch protection 拦截后走设计内的 fallback 路径,合并后经标准 release.yml 发布 v0.1.178。
  2. 什么原因导致的:发布机制层面是 branch protection 的正常防护触发 fallback;内容层面(dsh boot crash on mixed copies: global >=0.1.176 bundle yml (bare name) + profile copy <=0.1.175 (exports["."]=CLI) — window opened by manual npm i -g, self-heal blocked by the crash itself #1803)是 dsh 从全局安装读 bundle yml、却从各 profile 自己的 node_modules 解析入口模块,混合版本时 bare 名解析到旧包 CLI 根(零导出)导致启动崩溃并堵死自愈。
  3. 怎么修复的:release commit 本身只做版本号 bump(已逐行核实);内容修复 = 全局安装的周期性检查发现落后的 registry-pin profile 副本时,经 dsh 自己的插件渠道收敛,每周期重试直至成功,同步时静默零 spawn。
  4. 是否回归问题:无。触碰路径逐项清点见上;两处有意变更均已披露(in-step skip、CLI 输出格式);一个既有的跨 tag 通道下调边界残留(非本次引入)。
  5. 是否破坏缓存:否。wire/session/persistence/prefix cache 全部未触碰,更新锁与节流协议原样复用。
  6. 是否改了设计方向:否。仍在 dsh plugin-market installs never auto-update: the refresh chain's only trigger is a global bili self-update #1196/native模式下自动更新问题需要解决 #991 契约内(每个副本有活的升级路径、自愈走 owner 认可渠道),只是给 dsh 通道补了一个触发源。
  7. 是否引入新的配置:否。无新 BILI_* env、无 config.json 字段、无 CLI flag。

判定:可合——且已合并、CI 全绿、v0.1.178 已在 npm live。收工。

@ranxianglei
ranxianglei deleted the 2026-10-01_release-v0.1.178 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