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

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-28 07:33:54 +00:00
parent df186b0f3a
commit 15fe52be36
3 changed files with 20 additions and 17 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": "2f3e81fec203bc3491962439a80cb6fed36873f4",
"syncedAt": "2026-04-28T07:28:15.712Z"
"sha": "f5a7632ffc903f1118c97872cc7392e6f6eb9c69",
"syncedAt": "2026-04-28T07:32:23.678Z"
}

27
docs/ci.md
View File

@ -138,19 +138,20 @@ 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.
Package Acceptance has a bounded legacy-compatibility window for already
published packages through `2026.4.25`, including `2026.4.25-beta.*`. Those
allowances are documented here so they do not become permanent silent skips:
known private QA entries in `dist/postinstall-inventory.json` may warn when the
tarball omitted those files; `doctor-switch` may skip the
`gateway install --wrapper` persistence subcase when the package does not expose
that flag; `update-channel-switch` may prune missing `pnpm.patchedDependencies`
from the tarball-derived fake git fixture and may log missing persisted
`update.channel`; plugin smokes may read legacy install-record locations or
accept missing marketplace install-record persistence; and `plugin-update` may
allow config metadata migration while still requiring the install record and
no-reinstall behavior to stay unchanged. Packages after `2026.4.25` must satisfy
the modern contracts; the same conditions fail instead of warn or skip.
Package Acceptance has bounded legacy-compatibility windows for already
published packages. Packages through `2026.4.25`, including `2026.4.25-beta.*`,
may use the compatibility path for known private QA entries in
`dist/postinstall-inventory.json` that point at tarball-omitted files,
`doctor-switch` may skip the `gateway install --wrapper` persistence subcase
when the package does not expose that flag, `update-channel-switch` may prune
missing `pnpm.patchedDependencies` from the tarball-derived fake git fixture and
may log missing persisted `update.channel`, plugin smokes may read legacy
install-record locations or accept missing marketplace install-record
persistence, and `plugin-update` may allow config metadata migration while still
requiring the install record and no-reinstall behavior to stay unchanged. The
published `2026.4.26` package may also warn for local build metadata stamp files
that were already shipped. Later packages must satisfy the modern contracts; the
same conditions fail instead of warn or skip.
Examples:

6
docs/reference/RELEASING.md
View File

@ -423,8 +423,10 @@ to npm: private QA inventory entries missing from the tarball, missing
`gateway install --wrapper`, missing patch files in the tarball-derived git
fixture, missing persisted `update.channel`, legacy plugin install-record
locations, missing marketplace install-record persistence, and config metadata
migration during `plugins update`. Packages after `2026.4.25` must satisfy the
modern package contracts; those same gaps fail release validation.
migration during `plugins update`. The published `2026.4.26` package may warn
for local build metadata stamp files that were already shipped. Later packages
must satisfy the modern package contracts; those same gaps fail release
validation.
Use broader Package Acceptance profiles when the release question is about an
actual installable package: