@@ -111,9 +111,10 @@ Use this skill for release and publish-time workflow. Load `$release-private` if
111111- For fallback correction tags like ` vYYYY.M.D-N ` , the repo version locations still stay at ` YYYY.M.D ` .
112112- “Bump version everywhere” means all version locations above except ` appcast.xml ` .
113113- Release signing and notary credentials live outside the repo in the private maintainer docs.
114- - Every stable OpenClaw release ships the npm package and macOS app together.
115- Beta releases normally ship npm/package artifacts first and skip mac app
116- build/sign/notarize unless the operator requests mac beta validation.
114+ - Every stable OpenClaw release ships the npm package, macOS app, and signed
115+ Windows Hub installers together. Beta releases normally ship npm/package
116+ artifacts first and skip native app build/sign/notarize/promote unless the
117+ operator requests native beta validation.
117118- Do not let the slower macOS signing/notary path block npm publication once
118119 the npm preflight has passed. Keep mac validation/publish running in
119120 parallel, publish npm from the successful npm preflight, then start published
@@ -143,6 +144,17 @@ Use this skill for release and publish-time workflow. Load `$release-private` if
143144 at ` YYYY.M.D ` , but the mac release must use a strictly higher numeric
144145 ` APP_BUILD ` / Sparkle build than the original release so existing installs
145146 see it as newer.
147+ - Stable Windows Hub release closeout requires the signed
148+ ` OpenClawCompanion-Setup-x64.exe ` , ` OpenClawCompanion-Setup-arm64.exe ` , and
149+ ` OpenClawCompanion-SHA256SUMS.txt ` assets on the canonical
150+ ` openclaw/openclaw ` GitHub Release. Use the public ` Windows Node Release `
151+ workflow after the matching ` openclaw/openclaw-windows-node ` release exists;
152+ it verifies Authenticode signatures on Windows before uploading assets.
153+ - Website Windows Hub download links should target exact canonical
154+ ` openclaw/openclaw/releases/download/vYYYY.M.D/... ` assets for the current
155+ stable release, or ` releases/latest/download/... ` only after verifying the
156+ redirect resolves to that same tag, so the installable signed Windows artifact
157+ is visible from both the GitHub release page and openclaw.ai.
146158
147159## Build changelog-backed release notes
148160
@@ -178,6 +190,13 @@ Use this skill for release and publish-time workflow. Load `$release-private` if
178190 ` CHANGELOG.md ` version section, not highlights or an excerpt. When creating
179191 or editing a release, extract from ` ## YYYY.M.D ` through the line before the
180192 next level-2 heading and use that complete block as the release notes.
193+ - To update an existing GitHub Release body, resolve the numeric release id and
194+ patch that resource with the notes file as the ` body ` field:
195+ ` gh api repos/openclaw/openclaw/releases/tags/vYYYY.M.D --jq .id ` , then
196+ ` gh api -X PATCH repos/openclaw/openclaw/releases/<id> -F body=@/tmp/notes.md ` .
197+ Do not trust ` gh release edit --notes-file ` or ` --input ` JSON if verification
198+ disagrees; verify with ` gh api repos/openclaw/openclaw/releases/<id> ` because
199+ the tag lookup and ` gh release view ` can lag or show stale body text.
181200- When preparing release notes, scan ` src/plugins/compat/registry.ts ` and
182201 ` src/commands/doctor/shared/deprecation-compat.ts ` for compatibility records
183202 with ` warningStarts ` or ` removeAfter ` within 7 days after the release date.
0 commit comments