Skip to content

release v0.1.140 - #1191

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-23_release-v0.1.140
Sep 23, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-23_release-v0.1.140

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

```

@ranxianglei
ranxianglei merged commit 75fbeb2 into master Sep 23, 2026
8 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-23_release-v0.1.140 (3ecefc4)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-1191

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

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr1191.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] 🏷 Verified — this release is already complete; no further action needed from me.

This was the auto-fallback PR from the one-click release workflow (direct push to master blocked by branch protection). Per the [PR]/ework-agent-pr rule I did not redo or modify anything — I fetched the branch and verified the full chain:

  • Merged: PR release v0.1.140 #1191 (2026-09-23_release-v0.1.140 → master) was merged by @ranxianglei at 2026-09-23 14:50 UTC (merge commit 75fbeb22).
  • Release-commit discipline: the head commit release v0.1.140 (3ecefc42) changes ONLY package.json ("version": "0.1.139" → "0.1.140") and package-lock.json (matching version fields) — clean one-version-one-commit, no bundled content.
  • Tag: v0.1.140 points at merge commit 75fbeb22 on master.
  • Published: npm billion-context@latest = 0.1.140, published 2026-09-23 15:30 UTC (~40 min after merge — release.yml CI ran the standard flow as designed).
  • No drift: master's package.json now reads 0.1.140, matching npm latest.

The changelog in the PR body matches what landed on master since v0.1.139 (CCR kernel-native switch #1097, fetch-guard fixes #1158, zcode native lane #1145/#1151, stable-system anchor #1085, session-file GC #1082, codex UA fix #1169, acp-kernel 0.0.82→0.0.84).

中文摘要:这是 one-click release 被 branch protection 挡下后的 fallback PR,已由 @ranxianglei 手动合并并经 release.yml 自动发布 v0.1.140(npm latest 已上线、tag 指向合并提交、release commit 仅含版本号变更、master 与 npm 版本一致无漂移),发布链路完整无异常,bot 无需再做任何操作。

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