Repository navigation
docs(AGENTS): release workflow gains the release-notes entry step (#1870) - #1877
Conversation
) §5 standard flow: new step 4 'Add the release-notes entry' (same PR, its own commit — preserves one-version-one-commit; tier semantics; never hand-edit the companion package version), steps renumbered 4-8 → 5-9. One-click fast path: prerequisite paragraph (entry must be merged to master BEFORE dispatch — the workflow aborts otherwise) + drift-guard item mentions the check. Details live in release-notes/README.md.
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.1874-pr.1877.1c0c4ccThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr1877.tgz
npm install -g packageInstall instructions are refreshed on each push. |
…, not the drift guard (#1877 review) In release-manual.yml the 'Drift guard' step only does master==npm-latest, already-published and 0.0.x-floor checks; the release-notes entry is verified by the separate 'Verify release-notes entry (#1870)' step that follows it. The one-click list item 1 conflated the two.
[bot] 🏷 PR #1877 Review 结论 审查方式:拉取本 PR diff,逐条对照 companion PR #1873 的实际代码( 结构化七问
顺手修掉的小问题(独立标注 commit CI:旧 head ecb9208 除 合并顺序:如你所说两种顺序都可以;不过我确认过 master 上目前还没有 结论:内容准确、声明全部经代码核实、diff 干净(单文件 +37/−9,外加上面 3 行措辞修正);CI 转绿即可合并。 |
Companion to #1873: AGENTS.md §5 documented the release flow before release-notes existed, so an agent following only AGENTS.md would miss the entry and trip the new dispatch/publish gates.
release-notes/README.md(from feat: tiered release-notes visibility (#1870) #1873); AGENTS.md only carries the operational step.Docs-only; no code paths touched. Can merge in either order relative to #1873 — but merging #1873 first means the gate is live the moment this doc lands.