docs(release): document mac source ref fallback · openclaw/openclaw@f96a8f6
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 |
|---|
@@ -75,6 +75,14 @@ Use this skill for release and publish-time workflow. Keep ordinary development
|
75 | 75 | parallel, publish npm from the successful npm preflight, then start published |
76 | 76 | npm install/update, Docker, and Parallels verification while mac artifacts |
77 | 77 | continue. |
| 78 | +- If mac packaging needs release-branch-only fixes after the stable npm package |
| 79 | + or GitHub tag is already published, do not create a `vYYYY.M.D-N` correction |
| 80 | + tag just to change the workflow source. Dispatch the private mac workflows for |
| 81 | + the original `tag=vYYYY.M.D` with `source_ref=release/YYYY.M.D` and |
| 82 | +`public_release_branch=release/YYYY.M.D`; provenance checks must prove the |
| 83 | + source SHA descends from the tag and validation/preflight use the same source. |
| 84 | + Reserve `vYYYY.M.D-N` correction tags for cases where the published mac |
| 85 | + version/build identity itself must move to a newer Sparkle build. |
78 | 86 | - 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. |
79 | 87 | - That shared production Sparkle feed is stable-only. Beta mac releases may |
80 | 88 | upload assets to the GitHub prerelease, but they must not replace the shared |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
