Skip to content

release v0.1.175 - #1739

Closed
github-actions[bot] wants to merge 2 commits into
masterfrom
2026-09-30_release-v0.1.175-053442
Closed

github-actions[bot] wants to merge 2 commits into
masterfrom
2026-09-30_release-v0.1.175-053442

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

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 中文摘要:这个 release PR 是纯版本号 bump(0.1.174→0.1.175),代码与 changelog 已逐项核对无误,v0.1.174→HEAD 版本区间回归审计未发现回归,内容上可以合并;唯一阻塞是 PR 的全部 CI runs 停在 action_required 等待人工批准(#772 的 push-CI 自动变绿机制本次未生效,已单独立项 #1744),请人工批准后合并。


Reviewed this auto-fallback release PR per the release-window audit protocol (②b). I did not redo any work — verification only. Merging stays human-only.

① Direction / provenance

Auto-fallback from the one-click workflow (run id 36673740079, 05:30Z): direct push to master was rejected with GH006 … Changes must be made through a pull request + 4 of 4 required status checks expected, so the release landed on a branch and this PR was opened. That matches the documented fallback path in AGENTS.md §5.

③ Code audit (the PR diff itself)

  • Head 2026-09-30_release-v0.1.175-053442 @ 3df6a8b = origin/master (27c8774a) + exactly one commit release v0.1.175. Merge-base = current master HEAD → fresh base, no rebase needed.
  • Diff is exactly 2 files / 3 lines: "version" 0.1.174 → 0.1.175 in package.json and both occurrences in package-lock.json. Nothing else. Conforms to the one-version-one-commit convention (§4).
  • Drift guard: npm latest = 0.1.174 = master's version; 0.1.175 not yet published. ✓
  • Changelog accuracy: the "Changes since v0.1.174" list matches git log v0.1.174..master exactly — all 14 non-merge content commits present, none missing, none invented. ✓

②b Version-window regression audit (v0.1.174 → HEAD, 23 commits)

Walked every fix/feat in the window against the pre-existing behavior each touched path carries:

Change Old → New Verdict
#1688 transport retry main model-request path: fail-fast on fail-fast transport error → bounded transparent retry intentional, disclosed in its PR; other paths untouched
#1718 log privacy (×3) bili.log carried conversation-derived text / raw upstream URLs / non-loopback IP literals / credential-shaped secrets → length-only fingerprints, salted msg ids, masked IPs/URLs, scrubbed secrets intentional privacy hardening; log-content change only
#1720 tag-echo filter prose between paired render tags swallowed → kept intentional
#1712/#1713 decompress ranges blank range fields rejected-ish; range args advertised even where CCR can't arm → blanks treated as omitted, args not advertised where inapplicable intentional
#1699 opencode v2 title-gen classified by token budget → classified by host-declared intent intentional
#1662 fetch chain unbounded against coexisting re-wrapping plugins → bounded intentional (recursion bound)
#1657 unrouted-endpoint reporting reported for all methods → POST only intentional log-noise reduction
#1702 subagent sidecar opencode sub-agent session ids lost across folds → preserved via structured-field sidecar additive capability; I inspected the last delta (#1722) directly — purely additive request-path logic (attachSubagentSessions in prepare*, sidecar sync in applyRanges), no boot/port/wire-shape changes
3 test-only commits (e2e hardening) n/a no runtime behavior

None of the window's commits touch src/update.ts, the release infra, the acp-kernel pin, message-ref/id logic, or security (MITM/CA/credentials). Each landed individually with its own review and green CI on its own head.

本版本引入回归:无。 All behavior changes above are intentional and were disclosed in their respective PRs; this table doubles as the release-notes material.

CI status — the actual blocker ⚠️

  1. All 9 pull_request workflow runs on the PR head are completed / action_required — gated, waiting on human approval; they will not go green on their own.
  2. No push-event CI run exists on the fallback branch (verified exhaustively over the creation time window), even though the same workflow's GITHUB_TOKEN pushes to master did trigger push-CI for v0.1.173/v0.1.174. So the 专用:发布新版本pr #772 mechanism AGENTS.md §5 relies on ("ci.yml also runs on pushes to release branches → auto-PR immediately mergeable") did not fire under the current branch protection. Filed one-click release fallback PRs are not immediately mergeable under current branch protection (#772 push-CI mechanism never fires) #1744 with full repro, hypotheses, and a concrete fix (explicit workflow_dispatch of ci.yml with the branch ref after the fallback push).
  3. Base-tree flake (not a blocker, FYI): on master HEAD 27c8774a, matrix cell test (ubuntu-latest, node 22) failed — claude-native hook e2e "a healthy proxy on ANOTHER port is never attached (static URL)": the spawned proxy child exited with code 1 before becoming healthy. Assessed as an environmental flake, not a window regression: the identical test passed on ubuntu-latest/node-24 at the same second on the same sha (win-22/win-24 also green); no commit in v0.1.174..HEAD touches claude-native (checked per-commit); the previous 8 master pushes were fully green. If it reproduces when you approve the gated runs, just re-run that job.

What's needed from a human

  1. Approve the gated CI runs on this PR (or bypass protection) and merge — merge is human-only.
  2. Optional cleanup: a stale duplicate branch 2026-09-30_release-v0.1.175 (commit 39dc7dc9, based on 5c9c1470 — predates fix: preserve opencode sub-agent session ids across folds via structured-field sidecar (#1702) #1722) exists from an earlier same-day attempt. Content-equivalent for the bump but confusing alongside this PR's branch; safe to delete.

@ranxianglei ranxianglei mentioned this pull request Sep 30, 2026
@github-actions

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-09-30_release-v0.1.175-053442 (8834907)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1698-pr.1739.5e3a232

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

Install instructions are refreshed on each push.

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