openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@ba0f2e948f

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-29 02:51:07 +00:00
parent 9448fbd8d6
commit fa33facb0a
2 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "18237bc01512b05cb7b5b795955485fbb7393abb",
"syncedAt": "2026-04-29T02:43:41.978Z"
"sha": "ba0f2e948fc0a3cfcb03b3ddf6329197203d540d",
"syncedAt": "2026-04-29T02:49:40.192Z"
}

7
docs/ci.md
View File

@ -45,6 +45,13 @@ provider failures easier to rerun and diagnose. The aggregate
`native-live-extensions-media-music` shard names remain valid for manual
one-shot reruns.
The native live media shards run in
`ghcr.io/openclaw/openclaw-live-media-runner:ubuntu-24.04`, built by the
`Live Media Runner Image` workflow. That image preinstalls `ffmpeg` and
`ffprobe`; media jobs only verify the binaries before setup. Keep Docker-backed
live suites on normal Blacksmith runners, because container jobs are the wrong
place to launch nested Docker tests.
`OpenClaw Release Checks` uses the trusted workflow ref to resolve the selected
ref once into a `release-package-under-test` tarball, then passes that artifact
to both the live/E2E release-path Docker workflow and the package acceptance