From 15fe52be362e40dd6123a72196487a73d6c142e7 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Tue, 28 Apr 2026 07:33:54 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@f5a7632ffc903f1118c97872cc7392e6f6eb9c69 --- .openclaw-sync/source.json | 4 ++-- docs/ci.md | 27 ++++++++++++++------------- docs/reference/RELEASING.md | 6 ++++-- 3 files changed, 20 insertions(+), 17 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index b78a80b0a..69fae5c35 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -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" } diff --git a/docs/ci.md b/docs/ci.md index 5448a9bc2..42e8fabf9 100644 --- a/docs/ci.md +++ b/docs/ci.md @@ -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: diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md index ef089833a..dc1269145 100644 --- a/docs/reference/RELEASING.md +++ b/docs/reference/RELEASING.md @@ -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: