Repository navigation
[PR] align master with v0.1.207 (shipped from bugfix-v0.1.206) - #4673
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5717-pr.4673.7ef53a2This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4673.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复。 本 PR 取代已关闭的 #4659(同一目的——把已发布的 v0.1.207 版本对齐进 master),但机制不同:#4659 用 lane 侧 head( 标签: 正在核验(完成后给结构化八问结论):
|
(ai: vllm-qwen/qwen3.8-27b) 核验完成(分支已拉取,逐条对照 git 对象与 CI 日志)。issue 正文的四个结构性声明全部属实: ① head 树纯度 — ② 所有已发布代码已在 master — lane 独有提交逐条找到 master 对应物:#4390 族(f013414/1418989de/f0b3e8ab2,经 #4395,master 另有 daac3f4)、#4444(07f9288,#4451)、#4506(8eb194e,#4511)、#4215(85af00f)、#4264(c1272ae)、#4265(ea712f8 + ce751c5)、#4585 de-export——最后一条按内容核对: ③ release-notes 0.1.207 条目不带入 — tag v0.1.207 的账本含该条目(updated 2026-10-24);PR head 与 master@28b667b9 的账本逐字相同(updated 2026-10-21,最新条目 0.1.203)。owner 决定已落实。✅ ④ P4 自动切 lane — 读了 CI 状态(继承性红,证据如下) — head ec75f5d:gate/guard 类全绿(32 success,e2e 车道按计划 skip),test 分片 6 红。取 windows-22/4 分片日志与 master 自己 tip(d1b46fc)的同名分片日志逐行对比:两边失败的是完全相同的 7 个测试(均为重启家族: 结构化八问
判定:结构核验全过,可合——待 test 分片随 master 转绿即可合并(当前红为继承性,归属 #4599,本 PR 无需也不应自行处理)。合并是人工操作,我不代劳。合并后留意 P4 评论确认 |
(ai: vllm-qwen/qwen3.8-27b) CI 终态补记(上一条回复后分片已全部跑完):全部 gate/guard 门通过(39 success——含本 PR 直接相关的 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.835-master.ac844fa # this exact build
npm install -g billion-context@master # always the newest merged build
|
Brings the shipped v0.1.207 version bump into master — the v3 alignment step (replaces #4659, whose lane-side head cannot pass lane-leak-guard: resolving its conflicts requires merging master into a
bugfix-v*lane, which that guard forbids by design).Content: master @ 28b667b + one isolated
release v0.1.207commit (package.json + package-lock only). All shipped code already lives on master (the lane's fixes were carried there as cherry-picks and evolved further). The 0.1.207 release-notes entry is intentionally NOT carried (owner call — ledger stays as-is; the published tarball keeps its own copy).On merge: release-bugfix.yml P4 recognizes this exact PR shape (head=
bugfix, alignment title) and auto-cuts the next lanebugfix-v0.1.207from tag v0.1.207, pre-bumped to 0.1.208.Note: the
testshards currently fail on master's own tip (6/11 red, the #4599 sentinel firefight — e.g. refLedgerAligned restart family fails in sharded runs while passing standalone). This PR's tree is master + version only, so it inherits exactly master's health and goes green when master does.Supersedes #4659 (kept open there until this one is confirmed).