Repository navigation
ci: persist bugfix release channel + v0.1.182 release-note (#2011) - #2015
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2043-pr.2015.464d43aThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2015.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 Review 完成:内容可合;CI 红为继承自 master 的已知红(#2003),与本 PR 无关。 建议先合 #2006 清红,再合本 PR。以下为逐项结论(代码已对 master 逐文件核对,CI 日志已拉取分析)。 独立验证过的关键声明
结构化七问
CI 状态与查重
小发现(仅报告,未动你的分支): 收工判定:#2015 内容本身可合,mergeable_state=blocked 纯属继承红。推荐顺序:先合 #2006(master 转绿)→ 本 PR 经 merge ref 自动重跑转绿 → 合入。若赶时间,owner 也可带红直合本 PR(enforce_admins=false 允许,红与它无关)——但按 §7.4,发布工作流类变更本就留给人工合并。 |
|
小发现(仅报告,未动你的分支):reference/release.md 目前不记载这条常备 bugfix 通道,PR 固化为 standing capability 后文档有缺口。因你明确限定「ONLY these two files」,我没有往分支推文档 commit;需要的话我可以在合并后开一个小 follow-up PR 补齐 §5 一节。 直接修复 |
[bot] 🏷 已直接修复并推上分支:commit 改动内容(纯文档,2 文件,+42/-1):
顺带状态更新:我动手期间 #2007(typecheck 修复)已合入 master,分支也 rebase 到了新 master——之前 review 报告的继承红(#2003 那 12 条类型错误)随之消除。新 head 收工判定:文档缺口已补,CI 全绿,PR 具备合并条件,留待人工合并。 |
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:.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).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
.github/is outsidefiles[]); 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.