docs(release): decouple npm publish from mac release · openclaw/openclaw@599dd38
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 |
|---|
@@ -70,6 +70,11 @@ Use this skill for release and publish-time workflow. Keep ordinary development
|
70 | 70 | - Every stable OpenClaw release ships the npm package and macOS app together. |
71 | 71 | Beta releases normally ship npm/package artifacts first and skip mac app |
72 | 72 | build/sign/notarize unless the operator requests mac beta validation. |
| 73 | +- Do not let the slower macOS signing/notary path block npm publication once |
| 74 | + the npm preflight has passed. Keep mac validation/publish running in |
| 75 | + parallel, publish npm from the successful npm preflight, then start published |
| 76 | + npm install/update, Docker, and Parallels verification while mac artifacts |
| 77 | + continue. |
73 | 78 | - The production Sparkle feed lives at `https://raw.githubusercontent.com/openclaw/openclaw/main/appcast.xml`, and the canonical published file is `appcast.xml` on `main` in the `openclaw` repo. |
74 | 79 | - That shared production Sparkle feed is stable-only. Beta mac releases may |
75 | 80 | upload assets to the GitHub prerelease, but they must not replace the shared |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
