diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 033ae0737..e97038d26 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "cfca2d4051dce6b135b00de24e59f313b145f85a", - "syncedAt": "2026-04-28T02:42:07.331Z" + "sha": "129b996a4e57b16659e041868c2f09c7a04fb3cf", + "syncedAt": "2026-04-28T02:53:17.961Z" } diff --git a/docs/.generated/plugin-sdk-api-baseline.sha256 b/docs/.generated/plugin-sdk-api-baseline.sha256 index 73bf91a44..34b1cc967 100644 --- a/docs/.generated/plugin-sdk-api-baseline.sha256 +++ b/docs/.generated/plugin-sdk-api-baseline.sha256 @@ -1,2 +1,2 @@ -6c33fafd66396c2c769b8f8d1f5d0792beb8b4b2d23b5f0323ff2bb2d0a79805 plugin-sdk-api-baseline.json -27336f313c029843be409d22d79caf6f45884cf37458d9f52c0a88c4e8b268fd plugin-sdk-api-baseline.jsonl +343a555f212dd5ebf26dccbefff1cb4b56a08e4dcc2c801ac7ab5fb98973192a plugin-sdk-api-baseline.json +02aaccbe13f261de2d41fcb4270fc9ae70b931966089e56d21a4ebc8e80c8821 plugin-sdk-api-baseline.jsonl diff --git a/docs/ci.md b/docs/ci.md index 58cdb0695..5448a9bc2 100644 --- a/docs/ci.md +++ b/docs/ci.md @@ -14,10 +14,14 @@ manual `CI` workflow with that target, and dispatches `OpenClaw Release Checks` for install smoke, package acceptance, Docker release-path suites, live/E2E, OpenWebUI, QA Lab parity, Matrix, and Telegram lanes. It can also run the post-publish `NPM Telegram Beta E2E` workflow when a published package spec is -provided. The umbrella records the dispatched child run ids, and the final -`Verify full validation` job re-checks the current child run conclusions. If a -child workflow is rerun and turns green, rerun only the parent verifier job to -refresh the umbrella result. +provided. `release_profile=minimum|stable|full` controls the live/provider +breadth passed into release checks: `minimum` keeps the fastest OpenAI/core +release-critical lanes, `stable` adds the stable provider/backend set, and +`full` runs the broad advisory provider/media matrix. The umbrella records the +dispatched child run ids, and the final `Verify full validation` job re-checks +the current child run conclusions and appends slowest-job tables for each child +run. If a child workflow is rerun and turns green, rerun only the parent +verifier job to refresh the umbrella result and timing summary. For recovery, `Full Release Validation` and `OpenClaw Release Checks` both accept `rerun_group`. Use `all` for a release candidate, `ci` for only the @@ -33,12 +37,19 @@ runs it as named shards (`native-live-src-agents`, `native-live-src-gateway-backends`, `native-live-test`, `native-live-extensions-a-k`, `native-live-extensions-l-n`, `native-live-extensions-openai`, `native-live-extensions-o-z-other`, -`native-live-extensions-xai`, and split media audio/music/video shards) through -`scripts/test-live-shard.mjs` instead of one serial job. That keeps the same -file coverage while making slow live provider failures easier to rerun and -diagnose. The aggregate `native-live-extensions-o-z` and -`native-live-extensions-media` shard names remain valid for manual one-shot -reruns. +`native-live-extensions-xai`, split media audio/video shards, and +provider-filtered music shards) through `scripts/test-live-shard.mjs` instead +of one serial job. That keeps the same file coverage while making slow live +provider failures easier to rerun and diagnose. The aggregate +`native-live-extensions-o-z`, `native-live-extensions-media`, and +`native-live-extensions-media-music` shard names remain valid for manual +one-shot reruns. + +`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 +shard. That keeps the package bytes consistent across release boxes and avoids +repacking the same candidate in multiple child jobs. `Package Acceptance` is the side-run workflow for validating a package artifact without blocking the release workflow. It resolves one candidate from a diff --git a/docs/plugins/sdk-testing.md b/docs/plugins/sdk-testing.md index 495f4fa05..25898ea4e 100644 --- a/docs/plugins/sdk-testing.md +++ b/docs/plugins/sdk-testing.md @@ -45,6 +45,9 @@ plugins. Prefer the focused subpaths below for new plugin tests. The broad `openclaw/plugin-sdk/testing` barrel is legacy compatibility only. +Repo guardrails reject new real imports from `plugin-sdk/testing` and +`plugin-sdk/test-utils`; those names remain only as deprecated compatibility +surfaces for external plugins and compatibility-record tests. ```typescript import { diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md index bc2b11976..ef089833a 100644 --- a/docs/reference/RELEASING.md +++ b/docs/reference/RELEASING.md @@ -237,6 +237,7 @@ gh workflow run full-release-validation.yml \ -f ref=release/YYYY.M.D \ -f provider=openai \ -f mode=both \ + -f release_profile=full \ -f evidence_package_spec=openclaw@YYYY.M.D-beta.N ``` @@ -248,12 +249,25 @@ install smoke, cross-OS release checks, live/E2E Docker release-path coverage, 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. +`npm_telegram` child is either successful or intentionally skipped. The final +verifier summary includes slowest-job tables for each child run, so the release +manager can see the current critical path without downloading logs. 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 `release_profile` to select live/provider breadth: + +- `minimum`: fastest release-critical OpenAI/core live and Docker path +- `stable`: minimum plus stable provider/backend coverage for release approval +- `full`: stable plus broad advisory provider/media coverage + +`OpenClaw Release Checks` uses the trusted workflow ref to resolve the target +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. + Use these variants depending on release stage: ```bash @@ -262,7 +276,8 @@ gh workflow run full-release-validation.yml \ --ref main \ -f ref=release/YYYY.M.D \ -f provider=openai \ - -f mode=both + -f mode=both \ + -f release_profile=stable # Validate an exact pushed commit. gh workflow run full-release-validation.yml \