From 1446d1ccc9e977a7416ad6461850fe56baaca23f Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Mon, 4 May 2026 06:32:21 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@d8da04e58eeddc19c53a0df3ecee7b21dce6f263 --- .openclaw-sync/source.json | 4 ++-- docs/help/testing.md | 3 +++ docs/reference/RELEASING.md | 1 + 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 7ec7edf96..71fb4ddc8 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "70850d15ee7ab0912779dccd0929fbb3c9acee8b", - "syncedAt": "2026-05-04T06:18:16.015Z" + "sha": "d8da04e58eeddc19c53a0df3ecee7b21dce6f263", + "syncedAt": "2026-05-04T06:30:16.601Z" } diff --git a/docs/help/testing.md b/docs/help/testing.md index 7382faaa5..e1e4fec4a 100644 --- a/docs/help/testing.md +++ b/docs/help/testing.md @@ -195,6 +195,9 @@ inside every shard. `OPENCLAW_QA_CONVEX_SITE_URL` and the role secret. If `OPENCLAW_QA_CONVEX_SITE_URL` and a Convex role secret are present in CI, the Docker wrapper selects Convex automatically. + - The wrapper validates Telegram or Convex credential env on the host before + Docker build/install work. Set `OPENCLAW_NPM_TELEGRAM_SKIP_CREDENTIAL_PREFLIGHT=1` + only when deliberately debugging pre-credential setup. - `OPENCLAW_NPM_TELEGRAM_CREDENTIAL_ROLE=ci|maintainer` overrides the shared `OPENCLAW_QA_CREDENTIAL_ROLE` for this lane only. - GitHub Actions exposes this lane as the manual maintainer workflow diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md index a0a658067..d5825ab98 100644 --- a/docs/reference/RELEASING.md +++ b/docs/reference/RELEASING.md @@ -211,6 +211,7 @@ Validation` or from the `main`/release workflow ref so workflow logic and against the published npm package using the shared leased Telegram credential pool. Local maintainer one-offs may omit the Convex vars and pass the three `OPENCLAW_QA_TELEGRAM_*` env credentials directly. +- To run the full post-publish beta smoke from a maintainer machine, use `pnpm release:beta-smoke -- --beta betaN`. The helper runs Parallels npm update/fresh-target validation, dispatches `NPM Telegram Beta E2E`, polls the exact workflow run, downloads the artifact, and prints the Telegram report. - Maintainers can run the same post-publish check from GitHub Actions via the manual `NPM Telegram Beta E2E` workflow. It is intentionally manual-only and does not run on every merge.