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
{{ message }}
This repository was archived by the owner on Apr 17, 2026. It is now read-only.
Copy file name to clipboardExpand all lines: RELEASE.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,15 +66,15 @@ grep -A 2 "^release:" .goreleaser.yml
66
66
- ✅ `checksum:` generates `checksums.txt` (used by npm postinstall verification)
67
67
- ✅ `release:` points to GitHub (uploads everything automatically)
68
68
69
-
**Ready to release.** The recommended path is now the manual `Prepare Release` workflow, which runs the full verification suite, pauses for approval, and only then creates the tag.
69
+
**Ready to release.** The recommended path is now the manual `Release` workflow, which runs the full verification suite, pauses for approval, creates the tag, and then finishes publishing in the same run.
70
70
71
71
## Releasing
72
72
73
73
## Manual Release Flow
74
74
75
75
1. Choose the branch, tag, or SHA you want to release.
76
-
`Prepare Release` now validates the requested version format and tag availability, then rewrites the npm package version inside the CI workspace for the dry-run steps.
77
-
2. Open **Actions → Prepare Release**.
76
+
`Release` now validates the requested version format and tag availability, then rewrites the npm package version inside the CI workspace for the dry-run steps.
77
+
2. Open **Actions → Release**.
78
78
3. Run it with:
79
79
-`version`: the release version, for example `0.8.0`
80
80
-`ref`: the branch, tag, or SHA you want to release
@@ -88,13 +88,21 @@ grep -A 2 "^release:" .goreleaser.yml
88
88
- GoReleaser snapshot
89
89
-`npm publish --dry-run`
90
90
5. After those pass, GitHub pauses at the `release-approval` environment gate.
91
-
6. Approve the run. The workflow creates and pushes `v0.8.0` from the exact tested commit SHA.
92
-
7. That tag triggers the `Release` workflow automatically.
91
+
6. Approve the run. The workflow creates and pushes `v0.8.0` from the exact tested commit SHA, then continues publishing from that tag in the same run.
92
+
7. Monitor the remaining publish jobs in the same workflow run:
93
+
- GitHub release binaries
94
+
- npm publish
95
+
- Docker image publish
96
+
- ClawHub skill publish
93
97
94
98
### Required GitHub setup
95
99
96
100
Configure a protected environment named `release-approval` with the required reviewers for the manual gate to be effective.
97
101
102
+
### Recovery publish
103
+
104
+
If a tag already exists and you need to retry publishing, use **Actions → Release / Manual Publish** with the existing tag, for example `v0.8.0`.
0 commit comments