@@ -69,9 +69,13 @@ Use this skill for release and publish-time workflow. Load `$release-private` if
6969 or clawgrit reports. Report regressions explicitly. A major regression is a
7070 release blocker unless the operator waives it or the data clearly proves
7171 infrastructure noise.
72-- Generate the changelog before version/tag preparation so the top changelog
73- section is deduped and ordered by user impact. Use
74-`$openclaw-changelog-update` for the rewrite.
72+- Generate the changelog before every beta, beta rerun, stable release, or
73+ stable rerun, before version/tag preparation. Use
74+`$openclaw-changelog-update` for the rewrite. Do not continue release prep if
75+ the target `CHANGELOG.md` section does not have `### Highlights`,
76+`### Changes`, and `### Fixes`, grouped by user-facing surface while
77+ preserving every relevant PR/issue ref and every human `Thanks @...`
78+ attribution in the grouped bullet.
7579- Do not create beta-specific `CHANGELOG.md` headings. Beta releases use the
7680 stable base version section, for example `v2026.4.20-beta.1` uses
7781`## 2026.4.20` release notes.
@@ -144,6 +148,9 @@ Use this skill for release and publish-time workflow. Load `$release-private` if
144148 section from history, not existing notes. Use the last reachable stable or
145149 beta release tag as the base, then inspect every commit through the target
146150 release SHA.
151+- The changelog rewrite is not optional for beta reruns: any `beta.N` after a
152+ rebase or backport must refresh the same stable-base `## YYYY.M.D` section
153+ before the new version/tag commit.
147154- Include both merged PR commits and direct commits on `main`. Direct commits
148155 matter: infer notes from their subject, body, touched files, linked issues,
149156 tests, and nearby code when no PR body exists.
@@ -157,6 +164,11 @@ Use this skill for release and publish-time workflow. Load `$release-private` if
157164- Add missed user-facing changes, remove internal-only noise, dedupe overlapping
158165 PR/direct-commit entries, and sort each section from most to least interesting
159166 for users.
167+- Group related highlights, changes, and fixes by user-facing surface and
168+ impact, but never lose traceability: each grouped bullet keeps every relevant
169+`#issue`, `(#PR)`, `Fixes #...`, and every human `Thanks @...` handle.
170+ Multiple thanks in one bullet are expected when multiple contributor PRs are
171+ grouped.
160172- Changelog entries should be user-facing, not internal release-process notes.
161173- GitHub release and prerelease bodies must use the full matching
162174`CHANGELOG.md` version section, not highlights or an excerpt. When creating
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。