docs(release): clarify unpublished beta tag movement · op...
steipete
·
2026-05-06
·
via Recent Commits to openclaw:main
File tree
.agents/skills/openclaw-release-maintainer
| Original file line number | Diff line number | Diff line change |
|---|
@@ -42,10 +42,12 @@ Use this skill for release and publish-time workflow. Keep ordinary development
|
42 | 42 | config footprint move, so do not blindly copy stale replacement annotations |
43 | 43 | into release notes. |
44 | 44 | - Do not delete or rewrite beta tags after their matching npm package has been |
45 | | - published. If a pushed beta tag fails preflight before npm publish, delete and |
46 | | - recreate the tag and prerelease at the fixed commit so npm prerelease versions |
47 | | - stay contiguous. If a published beta needs a fix, commit the fix on the |
48 | | - release branch and increment to the next `-beta.N`. |
| 45 | + published. If a pushed beta tag fails before npm publish, the version is not |
| 46 | + consumed: keep the same `-beta.N`, delete/recreate or force-move the git tag |
| 47 | + and prerelease to the fixed commit, and rerun preflight. Do not increment to |
| 48 | + the next beta number until the matching npm package has actually published. |
| 49 | + If a published beta needs a fix, commit the fix on the release branch and |
| 50 | + increment to the next `-beta.N`. |
49 | 51 | - For a beta release train, run the fast local preflight first, publish the |
50 | 52 | beta to npm `beta`, then run the expensive published-package roster focused |
51 | 53 | on install/update/Docker/Parallels/NPM Telegram. If anything fails, fix it on |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
