You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: "Draft or post OpenClaw beta/stable Discord release announcements from changelog, GitHub release, registry, and validation evidence. Use when announcing a beta, stable release, release candidate, or asking what users should test after an OpenClaw release."
4
+
---
5
+
6
+
# OpenClaw Release Announcement
7
+
8
+
Use with `release-openclaw-maintainer` after a beta or stable release is live.
9
+
Use with `openclaw-discord` when actually posting to Discord.
10
+
11
+
## Evidence First
12
+
13
+
Before drafting focus areas, read real release evidence:
14
+
15
+
1. Current GitHub release body for the tag.
16
+
2.`CHANGELOG.md` section for the released base version.
17
+
3. Commits since the previous shipped version or the operator-specified base.
18
+
4. Registry/package metadata for the exact version and current dist-tag.
19
+
5. Validation status that is relevant to user confidence.
20
+
21
+
Do not claim a full changelog audit unless you did it. If you only read the
22
+
generated release notes or top changelog section, say that and either audit
23
+
properly or draft with that limitation.
24
+
25
+
For beta focus areas, prioritize user-observable changes over internal test or
26
+
CI mechanics:
27
+
28
+
- install/update paths
29
+
- OS/platform-specific behavior
30
+
- Gateway startup/restart, config, and runtime behavior
31
+
- provider/model/runtime routing
32
+
- plugin loading and local plugin development
33
+
- channels and media paths
34
+
- security/data-loss/user-impact fixes
35
+
36
+
Do not let late release-branch fixes automatically dominate the announcement.
37
+
If the version includes a large delta from the previous shipped version, rank
38
+
focus areas by the whole release delta and expected user impact; mention late
39
+
fixes in their natural category.
40
+
41
+
## Required Copy
42
+
43
+
Every beta announcement must make beta status explicit and include:
44
+
45
+
- exact version, e.g. `OpenClaw 2026.5.25-beta.1`
46
+
- one-sentence risk framing: beta, useful for testing, not stable promotion
47
+
- focused test areas derived from evidence, not guesswork
48
+
- update command promoted near the top:
49
+
```sh
50
+
openclaw update --channel beta --yes
51
+
openclaw --version
52
+
```
53
+
- fresh install path:
54
+
`Install from https://openclaw.ai`
55
+
- GitHub release link
56
+
- concise validation note, without making CI the headline
57
+
58
+
Do not suggest npm install commands in beta announcements unless the operator
59
+
explicitly asks for npm-specific copy or troubleshooting text. It is fine to use
60
+
registry metadata as evidence; do not turn that into public install guidance.
61
+
62
+
For stable announcements, use the stable channel wording:
63
+
64
+
```sh
65
+
openclaw update --channel stable --yes
66
+
openclaw --version
67
+
```
68
+
69
+
Fresh installs still point to `https://openclaw.ai`.
70
+
71
+
## Style
72
+
73
+
- Discord Markdown, no tables.
74
+
- Keep it skimmable: short intro, bullets, commands, links.
75
+
- Lead with what users can feel or test, not proof plumbing.
76
+
- Mention validation only after install/update instructions.
77
+
- Be specific about where feedback is useful.
78
+
- Do not mention private local proof paths in public announcements.
79
+
- Do not overstate unverified platforms, channels, or provider behavior.
80
+
81
+
## Posting
82
+
83
+
When asked to post, use the configured Discord workflow from
84
+
`openclaw-discord` or the approved OpenClaw relay. Never print tokens.
85
+
For public channels, inspect the final body before sending.
short_description: "Draft Discord beta/stable release announcements from evidence."
4
+
default_prompt: "Use this skill to draft an OpenClaw beta or stable Discord announcement from changelog, release notes, npm/GitHub release proof, and validation evidence."
0 commit comments