Skip to content

ci: persist bugfix release channel + v0.1.182 release-note (#2011) - #2015

Merged
ranxianglei merged 4 commits into
masterfrom
2026-10-04_bugfix-release-channel
Oct 4, 2026
Merged

ranxianglei merged 4 commits into
masterfrom
2026-10-04_bugfix-release-channel

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Follow-up to the v0.1.182 emergency carve-out for #2011 (fractional max_tokens → upstream 400/422). The fix itself ships in #2012; this PR persists the two NON-CODE artifacts of that emergency onto master so they become a standing capability:

  1. .github/workflows/release-bugfix.yml — the dedicated bugfix carve-out publish channel used to ship v0.1.182. It publishes a ref's own tree (e.g. a released tag + one fix), strictly excluding unreleased master work, with guards (strictly-newer-than-npm, not-already-live, release-notes gate) and full pre-flight (npm ci + typecheck + test + build) before publish. It never touches or merges master. Byte-identical to the copy that published v0.1.182 (CI run 37139337532).
  2. release-notes/package.json — adds the v0.1.182 entry so the companion package publishes it (the carve-out did not reach master, so 0.1.182 users currently do not see the note in acp_status).

Scope

  • ONLY these two files. No proxy code, no version bump (master stays 0.1.181 → next normal release must be >= 0.1.183). Disjoint from fix(#2011): floor output-budget caps so max_tokens is always an integer #2012's files, so no conflict.
  • Runtime behavior change: none. A workflow file is not shipped in the tarball (.github/ is outside files[]); the release-notes entry only adds visibility text.

Why on master

v0.1.182 was already published via the carve-out branch (npm latest = 0.1.182, gitHead = 5a9d84a). Merging this makes the channel reusable for future hotfixes and closes the companion-notes gap. It does NOT re-publish anything.

Part of #2011; complements #2012.

@github-actions

github-actions Bot commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-04_bugfix-release-channel (c2e4ec8)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.2043-pr.2015.464d43a

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-pr2015.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] 🏷 Review 完成:内容可合;CI 红为继承自 master 的已知红(#2003),与本 PR 无关。 建议先合 #2006 清红,再合本 PR。以下为逐项结论(代码已对 master 逐文件核对,CI 日志已拉取分析)。

独立验证过的关键声明

结构化七问

  1. 是什么问题:v0.1.182 紧急 carve-out(bili 0.1.181:clampOutputBudget 把小数写进 max_tokens,上游 400 max_tokens: Input should be a valid integer / 422 Endpoint is unavailable #2011)的两个非代码产物没回落到 master——专用 hotfix 发布通道只存在于一次性分支、companion release-notes 包缺 0.1.182 记录。本 PR 把二者固化为常备能力。
  2. 什么原因导致的:carve-out 走的是旁路分支直接发布,npm latest 已到 0.1.182 但 master 树里没有通道文件和笔记条目——不是缺陷,是紧急路径的正常残留,本 PR 是补账。
  3. 怎么修复的:纯持久化,零代理代码、零行为逻辑新增。workflow 与 release.yml 同构(同一套权限最小集 contents:write+id-token:write、node22、Design: PR artifact publishing — stop dist-tag growth with single rolling tag + monotonic 0.0.x-pr versions #1385 sub-0.1.0 guard、preflight npm ci+typecheck+test+build 带 ACP_TEST_CLAUDE_NATIVE=1、prerelease→dev tag 逻辑、发版可见性:分级标签的 release 元数据(模型撰写摘要)+ 用户版跨 span 更新说明 + acp_status //acp 面板送达「更新已就绪待重启」(#1577 延伸) #1870 笔记门),外加三道针对「已发布版本+一个修复」场景的守卫:strictly-newer-than-npm(base 语义比较)、not-already-live(npm view billion-context@$VER)、concurrency group bugfix-release。release notes body 用 git describe --exclude v$VER* 划定 LAST..HEAD 而非 release.yml 的 generate_release_notes:true——对不含未发布 master 工作的 carve-out ref 这是正确选择。全程不 checkout/push/merge master ✓。
  4. 是否有回归问题:逐项清点触碰路径的既有行为——(a) release.yml 零改动;(b) release-notes.yml 触发 = 预期内的 companion 发包,校验约束已逐条本地核对通过;(c) 新触发面 push: bugfix-release/** 目前唯一命中分支是 carve-out 分支本身,重复推送会被 not-already-live 守卫拒掉(fail-closed);(d) .github/ 不在 files[] 内,不进 tarball,运行时零影响;(e) 配置面零新增(env/config/CLI 均无,workflow_dispatch 无输入参数)。一处精度澄清(非缺陷):按现行展示策略(Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #1977/fix(#1977): release-notes visibility surfaces only for critical-tier releases #1983,landing 晚于 v0.1.181 cut),recommended 级条目是 record-only、只有 critical 才面向用户 surfacing——所以这条笔记实际可见窗口是仍运行 pre-fix(#1977): release-notes visibility surfaces only for critical-tier releases #1983 bili(0.1.181/0.1.182 时代构建)的用户,正是本次紧急修复的目标人群;他们自动更新越过 fix(#1977): release-notes visibility surfaces only for critical-tier releases #1983 后条目留在记录里不再 nag,符合 Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #1977 设计意图。另有一处保守边界:base 语义比较在 npm latest 为 X-dev 预发布时会拒绝发布 stable X(c==0 判负)——方向是拒发而非降级,且已被 v0.1.182 实战验证,维持现状合理。
  5. 是否破坏缓存:不涉及(无缓存/重试/游标/去重键路径被触碰)。
  6. 是否改了设计方向:不涉及。是在既有发布管线旁加一条与 master 严格隔离的平行通道,数据流不变。
  7. 是否引入了新的配置:不涉及。

CI 状态与查重

小发现(仅报告,未动你的分支):reference/release.md 目前不记载这条常备 bugfix 通道,PR 固化为 standing capability 后文档有缺口。因你明确限定「ONLY these two files」,我没有往分支推文档 commit;需要的话我可以在合并后开一个小 follow-up PR 补齐 §5 一节。

收工判定:#2015 内容本身可合,mergeable_state=blocked 纯属继承红。推荐顺序:先合 #2006(master 转绿)→ 本 PR 经 merge ref 自动重跑转绿 → 合入。若赶时间,owner 也可带红直合本 PR(enforce_admins=false 允许,红与它无关)——但按 §7.4,发布工作流类变更本就留给人工合并。

@ranxianglei

Copy link
Copy Markdown
Owner Author

小发现(仅报告,未动你的分支):reference/release.md 目前不记载这条常备 bugfix 通道,PR 固化为 standing capability 后文档有缺口。因你明确限定「ONLY these two files」,我没有往分支推文档 commit;需要的话我可以在合并后开一个小 follow-up PR 补齐 §5 一节。

直接修复

@ranxianglei
ranxianglei merged commit a8731d7 into master Oct 4, 2026
14 checks passed
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 已直接修复并推上分支:commit c2e4ec88 docs(release): document the bugfix carve-out channel in release reference(additive,叠加在你 rebase 后的 head bc68ef85 之上)。

改动内容(纯文档,2 文件,+42/-1):

顺带状态更新:我动手期间 #2007(typecheck 修复)已合入 master,分支也 rebase 到了新 master——之前 review 报告的继承红(#2003 那 12 条类型错误)随之消除。新 head c2e4ec88 全量 CI 14/14 全绿(含 4 个 test job、version-guard、build-artifact、全部真客户端 lane 与 hermetic registry e2e),mergeable=true。

收工判定:文档缺口已补,CI 全绿,PR 具备合并条件,留待人工合并。

@ranxianglei
ranxianglei deleted the 2026-10-04_bugfix-release-channel 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