From 7248a7749f852c0c2e23a333a2899d520fa44fd8 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Thu, 23 Apr 2026 16:51:06 +0100 Subject: [PATCH] docs(release): clarify mac source variation policy --- .../openclaw-release-maintainer/SKILL.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/.agents/skills/openclaw-release-maintainer/SKILL.md b/.agents/skills/openclaw-release-maintainer/SKILL.md index c5cbf1fb9b9..27b31f8b1a3 100644 --- a/.agents/skills/openclaw-release-maintainer/SKILL.md +++ b/.agents/skills/openclaw-release-maintainer/SKILL.md @@ -75,14 +75,17 @@ Use this skill for release and publish-time workflow. Keep ordinary development parallel, publish npm from the successful npm preflight, then start published npm install/update, Docker, and Parallels verification while mac artifacts continue. -- If mac packaging needs release-branch-only fixes after the stable npm package - or GitHub tag is already published, do not create a `vYYYY.M.D-N` correction - tag just to change the workflow source. Dispatch the private mac workflows for - the original `tag=vYYYY.M.D` with `source_ref=release/YYYY.M.D` and - `public_release_branch=release/YYYY.M.D`; provenance checks must prove the - source SHA descends from the tag and validation/preflight use the same source. - Reserve `vYYYY.M.D-N` correction tags for cases where the published mac - version/build identity itself must move to a newer Sparkle build. +- Mac packaging may be built from a slight release-branch variation of the + tagged commit when the delta is mac packaging, signing, workflow, or + validation-only release machinery. If mac packaging needs release-branch-only + fixes after the stable npm package or GitHub tag is already published, do not + create a `vYYYY.M.D-N` correction tag just to change the workflow source. + Dispatch the private mac workflows for the original `tag=vYYYY.M.D` with + `source_ref=release/YYYY.M.D` and `public_release_branch=release/YYYY.M.D`; + provenance checks must prove the source SHA descends from the tag and + validation/preflight use the same source. Reserve `vYYYY.M.D-N` correction + tags for emergency hotfixes that must publish a new npm package/release + identity, not for ordinary mac-only packaging recovery. - 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. - That shared production Sparkle feed is stable-only. Beta mac releases may upload assets to the GitHub prerelease, but they must not replace the shared