@@ -25,6 +25,12 @@ Use this skill for release and publish-time workflow. Keep ordinary development
2525- Before release branching, commit any dirty files in coherent groups, push,
2626 pull/rebase, then run `/changelog` on `main` and commit/push/pull that
2727 changelog rewrite immediately before creating the release branch.
28+- During release planning, inspect `src/plugins/compat/registry.ts` before
29+ branching and again before final publish. For every deprecated or
30+ removal-pending compatibility record whose `removeAfter` date is on or before
31+ the release date, either remove the compatibility path where safe and
32+ validate the affected tests, or write down why removal is blocked and get
33+ explicit maintainer approval before shipping the expired compatibility path.
2834- Do not delete or rewrite beta tags after they leave the machine. If a
2935 published or pushed beta needs a fix, commit the fix on the release branch and
3036 increment to the next `-beta.N`.
@@ -116,6 +122,12 @@ Use this skill for release and publish-time workflow. Keep ordinary development
116122`CHANGELOG.md` version section, not highlights or an excerpt. When creating
117123 or editing a release, extract from `## YYYY.M.D` through the line before the
118124 next level-2 heading and use that complete block as the release notes.
125+- When preparing release notes, scan `src/plugins/compat/registry.ts` for
126+ plugin compatibility records with `warningStarts` or `removeAfter` within 7
127+ days after the release date. Add an `Upcoming deprecations` note to the
128+ release notes when any exist, including the compatibility code, target date,
129+ replacement, and a link to the record's `docsPath` or `/plugins/compatibility`
130+ when no more specific deprecation page exists.
119131- When cutting a mac release with a beta GitHub prerelease:
120132- tag `vYYYY.M.D-beta.N` from the release commit
121133- create a prerelease titled `openclaw YYYY.M.D-beta.N`
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。