Skip to content

[PR] fix(ci): post carry receipts with -F so the @- stdin field is parsed - #4519

Merged
ranxianglei merged 4 commits into
masterfrom
2026-10-24_carry-receipt-fix
Oct 24, 2026
Merged

ranxianglei merged 4 commits into
masterfrom
2026-10-24_carry-receipt-fix

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

(ai: zai/glm-5.3)

Fixes #4518

这是啥问题?

#4503 合并时打 backport 标签触发的真实首跑(09:55Z)证明新机器人主路径正确(自动切出 bugfix-v0.1.206 车道、检测 merge-commit、逐个 pick),但三处回执评论路径全坏:gh api ... -f body=@- 里小写 -f 不解析 @-(stdin 语法只在 -F/--field 生效),于是评论被发成字面字符串 "@-"——冲突清单与手动重放命令静默丢失。

改动

.github/workflows/backport.yml 三处(共 3 行,每行一个字符):-f body=@- → -F body=@-。

  • L79 fork head 的手动 cherry-pick 指引评论
  • L200 「no own commits / every pick conflicted」回执(含重放命令表)
  • L296 成功回执(carry PR 链接 + pin + 冲突状态)

为什么不是更大改动

gh help api:"if the value starts with @, the rest of the value is interpreted as a filename… Pass - to read from standard input" ——该解析归属 -F/--field;管道形态本身({ …; } | gh api …)保持不变。成功路径(#4503 之前从无人走到过)首次生产验证时即暴露本 bug,属回归级缺陷而非设计问题。

测试

  • YAML yaml.safe_load 通过;
  • 行为证据:修复前 run(workflow 394763171,09:55:10Z)三处中走到 L200 路径,POST 响应 body="@-"(comment 6382794648,已删);
  • 无 TS/源码改动,纯 workflow 单文件。

附带清理(同 commit 前已完成,API)

删除 #4503 上那条 "@-" 垃圾评论(id 6382794648)。#4503 的 3 个 pick 在 v0.1.206 车头上全部真实冲突(tag 之后 ci.yml/AGENTS.md/release.md 等被后续 PR 改动);因内容全是 .github/+文档(不进 npm 包、bot 从 master 读定义),无需补 carry——下次有人真正走「临时 fix 打标」路径时才会验证成功路径的回执渲染。

@github-actions

github-actions Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-24_carry-receipt-fix (95e024c)

Latest build — install this exact version

npm install -g billion-context@0.0.5471-pr.4519.a394e1c

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Recent builds (commit → version)

commit version build
95e024c billion-context@0.0.5471-pr.4519.a394e1c build
97f66a6 billion-context@0.0.5462-pr.4519.172cfb9 build
0455810 billion-context@0.0.5449-pr.4519.e491572 build
17ce719 billion-context@0.0.5439-pr.4519.425dfc5 build
acbfde1 billion-context@0.0.5438-pr.4519.ffba627 build
692ea79 billion-context@0.0.5437-pr.4519.3ac5098 build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr4519.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei ranxianglei changed the title fix(ci): post carry receipts with -F so the @- stdin field is parsed [PR] fix(ci): post carry receipts with -F so the @- stdin field is parsed Oct 24, 2026
@ranxianglei
ranxianglei force-pushed the 2026-10-24_carry-receipt-fix branch from 692ea79 to acbfde1 Compare October 24, 2026 10:23
@ranxianglei ranxianglei added the backport merge onto the patch train (bugfix-release/**) via the backport bot — set BEFORE merging label Oct 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

(ai: zai/glm-5.3) backport carry: every pick conflicted — nothing clean to push yet.

Conflicting picks (resolve manually on a fresh branch off bugfix-v0.1.206):

git checkout -b <fix-branch> origin/bugfix-v0.1.206
git cherry-pick -x 17ce7193   # resolve the <<<<<<< markers, then continue
git cherry-pick -x 04558109   # resolve the <<<<<<< markers, then continue
git push origin HEAD:<fix-branch>   # open a PR against bugfix-v0.1.206, label it backport-carry

ci-check and others added 2 commits October 24, 2026 19:10
…nc regenerates clean

#4505 added the flag (src/rollout.ts) and hand-wrote its doc rows but never registered it in website/config-reference/rollout.yaml, so every docs-sync run regenerates without the row and fails git diff --exit-code. Adding the seed entry restores idempotency; the generator normalizes the row (no backticks in generated descs, single default cell) and adds the env-map row it had been missing.
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.817-master.0022ae7 (rolling master tag).

npm install -g billion-context@0.0.817-master.0022ae7  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

@github-actions github-actions Bot mentioned this pull request Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport merge onto the patch train (bugfix-release/**) via the backport bot — set BEFORE merging

Projects

None yet

1 participant