Skip to content

release v0.1.137 - #1138

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-22_release-v0.1.137
Sep 22, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-22_release-v0.1.137

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

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.136

```

@ranxianglei
ranxianglei merged commit 3c8cc3b into master Sep 22, 2026
8 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-22_release-v0.1.137 (92635fd)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-1138

Each push to this PR publishes a new version under the pr-1138 npm tag.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr1138.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] 🏷 收到。这是 one-click release 的自动 fallback PR(master 直推被 branch protection 拦截)。初步核对:分支 2026-09-22_release-v0.1.137 的 diff 干净——仅 package.json 0.1.136→0.1.137 + package-lock.json 连带两处,符合 release-one-commit 规范;且该 PR 已经合入 master(merge commit 3c8cc3b)。但 npm latest 目前仍是 0.1.136,正在核对 release.yml 的 CI 状态,稍后更新结论。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 v0.1.137 发布全流程核验完成,一切正常。

核对结果(按 §5 流程逐项验证):

  1. Diff 干净 — 分支 2026-09-22_release-v0.1.137 相对 base(269fc54)的全部改动仅一个 commit 92635fd release v0.1.137:package.json 0.1.136→0.1.137 + package-lock.json 两处连带,无内容改动混入,符合 one-version-one-commit 规范。
  2. 已合入 master — merge commit 3c8cc3b(merged_at 2026-09-22T10:14:50Z)。
  3. release.yml CI 全绿 — run 35714920446:checkout → setup → branch-merge 检查 → build & test(typecheck+test+build)→ Create tag → Publish → Create GitHub Release,全部 success。Publish 步骤日志确认 npm publish --tag latest --access public 返回 + billion-context@0.1.137。
  4. 产物已上线 — tag v0.1.137 已创建;GitHub Release v0.1.137 于 10:16:50Z 发布;npm view billion-context version = 0.1.137。(发布后最初约 2 分钟 npm 元数据查询曾短暂 404,属注册表传播延迟,随后恢复正常。)
  5. changelog 与 master 实际内容一致 — 列出的四个 fix(fix: conclusive compress failure receipt when conversation is below minCompressRange #1128 compress-failure-receipt、fix: resolve search_context conversation_id "current" to current session #1127 search_context "current" 别名、fix: make effectiveTokenCount's stale-high bound image-aware #1120 image-aware stale-high bound、fix: side-request guard must not clamp on the host usage baseline (#1110) #1111 side-guard host usage baseline)均已先于版本 bump 合入 master。

一句话中文摘要:这是一个纯版本 bump 的 release fallback PR(one-click 直推被 branch protection 拦截后的正常兜底),diff 干净、CI 全绿、npm latest 已确认为 0.1.137,无需任何返工。

@ranxianglei
ranxianglei deleted the 2026-09-22_release-v0.1.137 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