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@1446069707

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-29 11:36:30 +00:00
parent 7b4dc730aa
commit ae7eb53c6c
3 changed files with 12 additions and 3 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": "f79553bef61f7b28a848d0c7dd6b04db99503083",
"syncedAt": "2026-04-29T11:24:58.782Z"
"sha": "1446069707bab832947cd909ad48e6bce052d586",
"syncedAt": "2026-04-29T11:35:02.058Z"
}

6
docs/ci.md
View File

@ -154,7 +154,11 @@ Cross-OS release checks still cover OS-specific onboarding, installer, and
platform behavior; package/update product validation should start with Package
Acceptance. The Windows packaged and installer fresh lanes also verify that an
installed package can import a browser-control override from a raw absolute
Windows path.
Windows path. The OpenAI cross-OS agent-turn smoke defaults to
`OPENCLAW_CROSS_OS_OPENAI_MODEL` when set, otherwise `openai/gpt-5.4-mini`, so
the install and gateway proof stays fast and deterministic. Dedicated live
provider/model lanes still cover broader model routing, including slower
frontier defaults.
Package Acceptance has bounded legacy-compatibility windows for already
published packages. Packages through `2026.4.25`, including `2026.4.25-beta.*`,

5
docs/reference/RELEASING.md
View File

@ -268,6 +268,11 @@ Use `release_profile` to select live/provider breadth:
ref once as `release-package-under-test` and reuses that artifact in both
release-path Docker checks and Package Acceptance. This keeps all
package-facing boxes on the same bytes and avoids repeated package builds.
The cross-OS OpenAI install smoke uses `OPENCLAW_CROSS_OS_OPENAI_MODEL` when the
repo/org variable is set, otherwise `openai/gpt-5.4-mini`, because this lane is
proving package install, onboarding, gateway startup, and one live agent turn
rather than benchmarking the slowest default model. The broader live provider
matrix remains the place for model-specific coverage.
Use these variants depending on release stage: