vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 05:50:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(release): clarify mac source variation policy

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-23 16:51:06 +01:00
parent baab065f05
commit 7248a7749f
1 changed files with 11 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
.agents/skills/openclaw-release-maintainer/SKILL.md
View File

@@ -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