From 3adff2fdbc6abf77fb09cc1951bd9396a49022c2 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Mon, 13 Apr 2026 13:03:48 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@6b6f0feb3c1ba0ad7f6105c9e09ed603ca700eb1 --- .openclaw-sync/source.json | 4 ++-- docs/reference/RELEASING.md | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index a3994217e..e98f75193 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "c4b8d6d5ab368225c89330a8b8663abc39e352fd", - "syncedAt": "2026-04-13T12:59:55.637Z" + "sha": "6b6f0feb3c1ba0ad7f6105c9e09ed603ca700eb1", + "syncedAt": "2026-04-13T13:03:48.326Z" } diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md index 97432a7fa..85224dbad 100644 --- a/docs/reference/RELEASING.md +++ b/docs/reference/RELEASING.md @@ -136,9 +136,9 @@ Rules: - Dist-tag sync mode must use a stable or correction tag, `preflight_only=false`, an empty `preflight_run_id`, `npm_dist_tag=latest`, and `promote_beta_to_latest=false` -- Promotion and dist-tag sync modes also require a valid `NPM_TOKEN` in the - `npm-release` environment because `npm dist-tag add` still needs regular npm - auth +- Promotion and dist-tag sync modes also require a valid `NPM_TOKEN` because + `npm dist-tag add` still needs regular npm auth; trusted publishing covers + the package publish path only ## Stable npm release sequence @@ -166,7 +166,7 @@ When cutting a stable npm release: `preflight_only=false`, `preflight_run_id` empty, and `npm_dist_tag=latest` The promotion and dist-tag sync modes still require the `npm-release` -environment approval and a valid `NPM_TOKEN` in that environment. +environment approval and a valid `NPM_TOKEN` accessible to that workflow run. That keeps the direct publish path and the beta-first promotion path both documented and operator-visible.