w-release
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAdvisory only. Do not bump versions, merge a release PR, or use publish credentials. Read the repository's release docs first.
- Diff against (feature PR) or the previous
maintag (release PR). List payload paths from those docs (Basilic example:v*,apps/api|web|mobile,packages/,tools/,scripts/,.cursor/, generator)..agents/ - Suggest a conventional title. Flag /
docs/chore/test/ciwhen payload paths changed unless the body hasstyle.skip-release: true - Note generator CLI, template include/exclude, and docs snapshot impact. Generated trees must not gain the documentation app or the generator.
- Draft user-facing changelog bullets and required adopter actions. Keep the repo's release changelog authoritative (Basilic: Release Please).
- Link tests, classification, and (on a release PR) scaffold acceptance. Stop if a human gate is missing.
仅提供建议。不要提升版本、合并发布 PR,或使用发布凭据。请先阅读仓库的发布文档。
- 与 (功能 PR)或上一个
main标签(发布 PR)进行差异比较。根据这些文档列出有效载荷路径(Basilic 示例:v*、apps/api|web|mobile、packages/、tools/、scripts/、.cursor/、generator)。.agents/ - 建议使用 conventional title。如果有效载荷路径发生变化,且正文未包含 ,则将
skip-release: true/docs/chore/test/ci标记出来。style - 说明 generator CLI、模板包含/排除规则以及文档快照的影响。生成目录中不得新增文档应用或 generator。
- 起草面向用户的更新日志要点和采用者需要采取的操作。仓库的发布更新日志应始终作为权威来源(Basilic:Release Please)。
- 关联测试、分类以及(在发布 PR 中)脚手架验收。如果缺少人工审核环节,则停止操作。