chore(sync): mirror docs from openclaw/openclaw@0931a1f11e

This commit is contained in:
openclaw-docs-sync[bot] 2026-04-27 12:34:34 +00:00
parent ca235091f7
commit 4c1cfc9653
2 changed files with 6 additions and 6 deletions

View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "252c63429ecf392e24dade8f72855fff5f63f89e",
"syncedAt": "2026-04-27T12:29:02.430Z"
"sha": "0931a1f11ea52a759ff81cf97345cf4ada7a2bc4",
"syncedAt": "2026-04-27T12:33:09.080Z"
}

View File

@ -232,7 +232,6 @@ branch, tag, or full commit SHA as `ref`:
gh workflow run full-release-validation.yml \
--ref main \
-f ref=release/YYYY.M.D \
-f workflow_ref=main \
-f provider=openai \
-f mode=both
```
@ -246,6 +245,10 @@ Package Acceptance with Telegram package QA, QA Lab parity, live Matrix, and
live Telegram. A full run is only acceptable when the `Full Release Validation`
summary shows `normal_ci` and `release_checks` as successful, and any optional
`npm_telegram` child is either successful or intentionally skipped.
Child workflows are dispatched from the trusted ref that runs `Full Release
Validation`, normally `--ref main`, even when the target `ref` points at an
older release branch or tag. There is no separate Full Release Validation
workflow-ref input; choose the trusted harness by choosing the workflow run ref.
Use these variants depending on release stage:
@ -254,7 +257,6 @@ Use these variants depending on release stage:
gh workflow run full-release-validation.yml \
--ref main \
-f ref=release/YYYY.M.D \
-f workflow_ref=main \
-f provider=openai \
-f mode=both
@ -262,7 +264,6 @@ gh workflow run full-release-validation.yml \
gh workflow run full-release-validation.yml \
--ref main \
-f ref=<40-char-sha> \
-f workflow_ref=main \
-f provider=openai \
-f mode=both
@ -270,7 +271,6 @@ gh workflow run full-release-validation.yml \
gh workflow run full-release-validation.yml \
--ref main \
-f ref=release/YYYY.M.D \
-f workflow_ref=main \
-f provider=openai \
-f mode=both \
-f npm_telegram_package_spec=openclaw@YYYY.M.D-beta.N \