@@ -5,7 +5,7 @@ description: "OpenClaw Tideclaw alpha/nightly release automation: isolated branc
5566# Nightly Release
778-Use for Tideclaw/OpenClaw alpha/nightly release automation, manual alpha triggers, beta prep, release-branch repair, and post-release forward-port.
8+Use for Tideclaw/OpenClaw alpha/nightly release automation, manual alpha triggers, beta prep, release-branch repair, and post-release forward-port. Load `$release-private` if it exists before using Tideclaw host paths, cron ids, or Discord routing ids.
991010## Policy
1111@@ -36,15 +36,15 @@ This is good for auditability if commits are clearly machine-authored and gated
3636- Branch prefix: `tideclaw/alpha/`
3737- Branch name: `tideclaw/alpha/YYYY-MM-DD-HHMMZ`
3838- Base: current `origin/main` SHA at trigger time.
39-- State file: `/root/tideclaw-workspace/.tideclaw-alpha-state.json`
39+- State file: resolve from `$release-private` on the Tideclaw host.
4040- Release tag: `vYYYY.M.D-alpha.N`
4141- npm dist-tag: `alpha`
42424343Do not reuse old alpha branches for a new run. If rerunning the same base SHA, create a new timestamped branch and record why.
44444545## Start
464647-1. Work in `/root/tideclaw-workspace/openclaw`.
47+1. Work in the Tideclaw host checkout from `$release-private`.
48482. Fetch first:
49495050```bash
@@ -66,7 +66,8 @@ git switch -c "$BRANCH" "$BASE_SHA"
6666Manual trigger:
67676868```bash
69-OPENCLAW_ALLOW_ROOT=1 openclaw cron run 8cfc76f6-d1b4-4608-85ec-1a659e76c0cd --expect-final --timeout 21600000
69+CRON_ID="<from release-private>"
70+OPENCLAW_ALLOW_ROOT=1 openclaw cron run "$CRON_ID" --expect-final --timeout 21600000
7071```
71727273## Discord Alpha Trigger
@@ -88,7 +89,7 @@ Rules:
88893. Follow the normal alpha workflow: reuse prior fixes, run local checks, fix on the alpha branch, run release CI, publish alpha after green gates, then forward-port reusable fixes via fixes-only PR.
89904. If another alpha/beta/stable release run is already active, report the active branch/run and stop.
90915. `#maintainers` trigger requires an explicit Tideclaw mention; do not react to unmentioned release chatter there.
91-6. Discord currently resolves `@Tideclaw` in `#maintainers` to managed role `<@&1505299068748824609>`. The live host hotfix treats that role mention as addressing bot user `1505297171623186432`; if the hotfix is absent, the message is dropped before this skill runs and must be resent after fixing preflight.
92+6. Resolve Discord role/user ids and live host hotfix notes from `$release-private`.
92939394## Discord Beta Trigger
9495@@ -119,7 +120,7 @@ Rules:
119120120121Before running checks, mine recent Tideclaw alpha branches for fixes already made during previous release attempts:
121122122-1. Read `/root/tideclaw-workspace/.tideclaw-alpha-state.json` for the last successful alpha branch and fix commit SHAs.
123+1. Read the Tideclaw state file from `$release-private` for the last successful alpha branch and fix commit SHAs.
1231242. List recent remote branches:
124125125126```bash
@@ -224,7 +225,7 @@ Release is not done until all are true:
224225- Release body links npm version page, registry tarball, integrity, and CI/proof.
225226- `npm view openclaw@<version>` shows the exact version, dist-tag `alpha`, tarball, integrity, and publish time.
226227- Installed/package smoke follows repo release docs.
227-- `/root/tideclaw-workspace/.tideclaw-alpha-state.json` records version, tag, base SHA, branch, fix commit SHAs, workflow run IDs, npm integrity, and timestamp.
228+- The Tideclaw state file from `$release-private` records version, tag, base SHA, branch, fix commit SHAs, workflow run IDs, npm integrity, and timestamp.
228229229230Final Discord summary in `#releases`:
230231此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。