vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 13:00:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify npm dist-tag auth

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-13 14:03:01 +01:00
parent c4b8d6d5ab
commit 6b6f0feb3c
2 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/RELEASING.md
View File

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