From e552d51d65dce9a7c58eff7daa17530d3389a170 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Thu, 7 May 2026 22:50:17 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@3a452a029ca42480d597bbab54e0c72c40051c00 --- .openclaw-sync/source.json | 4 ++-- docs/reference/RELEASING.md | 7 ++++++- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 6fdce0706..96c8eb912 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "5df08201ff50330c3d8b441c0e504ff5c4ec5a74", - "syncedAt": "2026-05-07T21:51:13.327Z" + "sha": "3a452a029ca42480d597bbab54e0c72c40051c00", + "syncedAt": "2026-05-07T22:48:14.352Z" } diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md index bc8b9325d..990979267 100644 --- a/docs/reference/RELEASING.md +++ b/docs/reference/RELEASING.md @@ -105,6 +105,9 @@ the maintainer-only release runbook. `OpenClaw Release Publish`, reusing the successful preflight artifact via `preflight_run_id`; stable macOS release readiness also requires the packaged `.zip`, `.dmg`, `.dSYM.zip`, and updated `appcast.xml` on `main`. + The private macOS publish workflow publishes the signed appcast to public + `main` automatically after release assets verify; if branch protection blocks + the direct push, it opens or updates an appcast PR. 11. After publish, run the npm post-publish verifier, optional standalone published-npm Telegram E2E when you need post-publish channel proof, dist-tag promotion when needed, verify the generated GitHub release page, @@ -272,7 +275,9 @@ Validation` or from the `main`/release workflow ref so workflow logic and not describe a stale CI layout - Stable macOS release readiness also includes the updater surfaces: - the GitHub release must end up with the packaged `.zip`, `.dmg`, and `.dSYM.zip` - - `appcast.xml` on `main` must point at the new stable zip after publish + - `appcast.xml` on `main` must point at the new stable zip after publish; the + private macOS publish workflow commits it automatically, or opens an appcast + PR when direct push is blocked - the packaged app must keep a non-debug bundle id, a non-empty Sparkle feed URL, and a `CFBundleVersion` at or above the canonical Sparkle build floor for that release version