Skip to content

release v0.1.173 - #1711

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-29_release-v0.1.173
Sep 29, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-29_release-v0.1.173

Conversation

@github-actions

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

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 收到。这是 one-click release workflow 的自动 fallback PR(直接推 master 被分支保护拦截)。按规范我不会重做——我会拉取分支核对代码、确认 CI 状态,然后向你报告结论。正在核对中,稍等。

@github-actions

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-09-29_release-v0.1.173 (e3db232)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1663-pr.1711.bf03c0b-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-pr1711.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit 75c1e75 into master Sep 29, 2026
13 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-29_release-v0.1.173 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