






















@@ -75,14 +75,17 @@ Use this skill for release and publish-time workflow. Keep ordinary development
7575 parallel, publish npm from the successful npm preflight, then start published
7676 npm install/update, Docker, and Parallels verification while mac artifacts
7777 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+- Mac packaging may be built from a slight release-branch variation of the
79+ tagged commit when the delta is mac packaging, signing, workflow, or
80+ validation-only release machinery. If mac packaging needs release-branch-only
81+ fixes after the stable npm package or GitHub tag is already published, do not
82+ create a `vYYYY.M.D-N` correction tag just to change the workflow source.
83+ Dispatch the private mac workflows for the original `tag=vYYYY.M.D` with
84+`source_ref=release/YYYY.M.D` and `public_release_branch=release/YYYY.M.D`;
85+ provenance checks must prove the source SHA descends from the tag and
86+ validation/preflight use the same source. Reserve `vYYYY.M.D-N` correction
87+ tags for emergency hotfixes that must publish a new npm package/release
88+ identity, not for ordinary mac-only packaging recovery.
8689- 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.
8790- That shared production Sparkle feed is stable-only. Beta mac releases may
8891 upload assets to the GitHub prerelease, but they must not replace the shared
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。