docs(release): require full GitHub release notes · openclaw/openclaw@2be2b24
steipete
·
2026-04-23
·
via Recent Commits to openclaw:main
File tree
.agents/skills/openclaw-release-maintainer
| Original file line number | Diff line number | Diff line change |
|---|
@@ -82,6 +82,10 @@ Use this skill for release and publish-time workflow. Keep ordinary development
|
82 | 82 | ## Build changelog-backed release notes |
83 | 83 | |
84 | 84 | - Changelog entries should be user-facing, not internal release-process notes. |
| 85 | +- GitHub release and prerelease bodies must use the full matching |
| 86 | +`CHANGELOG.md` version section, not highlights or an excerpt. When creating |
| 87 | + or editing a release, extract from `## YYYY.M.D` through the line before the |
| 88 | + next level-2 heading and use that complete block as the release notes. |
85 | 89 | - When cutting a mac release with a beta GitHub prerelease: |
86 | 90 | - tag `vYYYY.M.D-beta.N` from the release commit |
87 | 91 | - create a prerelease titled `openclaw YYYY.M.D-beta.N` |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
