From 49e83d68e3ccffba33c95d1541f474d825d2891a Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Thu, 7 May 2026 21:07:47 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@fa8a85586c007d6741843e872e2a63cd25be2b29 --- .openclaw-sync/source.json | 4 ++-- docs/reference/RELEASING.md | 10 +++++++--- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 785727bb6..0e24ba3da 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "6a8b4e422e820752435b81bc908b85114e4bc5de", - "syncedAt": "2026-05-07T20:28:03.852Z" + "sha": "fa8a85586c007d6741843e872e2a63cd25be2b29", + "syncedAt": "2026-05-07T21:05:35.519Z" } diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md index 01d64523f..bc8b9325d 100644 --- a/docs/reference/RELEASING.md +++ b/docs/reference/RELEASING.md @@ -81,6 +81,11 @@ the maintainer-only release runbook. dispatches all publishable plugin packages to npm and the same set to ClawHub in parallel, and then promotes the prepared OpenClaw npm preflight artifact with the matching dist-tag as soon as plugin npm publish succeeds. + After the OpenClaw npm publish child succeeds, it creates or updates the + matching GitHub release/prerelease page from the complete matching + `CHANGELOG.md` section. Stable releases published to npm `latest` become the + GitHub latest release; stable maintenance releases kept on npm `beta` are + created with GitHub `latest=false`. ClawHub publishing may still be running while OpenClaw npm publishes, but the release publish workflow prints the child run IDs immediately. By default it does not wait for ClawHub after dispatching it, so OpenClaw npm availability @@ -102,9 +107,8 @@ the maintainer-only release runbook. packaged `.zip`, `.dmg`, `.dSYM.zip`, and updated `appcast.xml` on `main`. 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, GitHub release/prerelease notes from the - complete matching `CHANGELOG.md` section, and the release announcement - steps. + dist-tag promotion when needed, verify the generated GitHub release page, + and run the release announcement steps. ## Release preflight