Skip to content

ci: remove redundant cli github release workflow #2487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Patrick-Erichsen wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −308
Open

ci: remove redundant cli github release workflow #2487

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
285 changes: 0 additions & 285 deletions .github/workflows/clawhub-cli-github-release.yml
View file
Open in desktop

This file was deleted.

27 changes: 4 additions & 23 deletions specs/deploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,29 +70,10 @@ CLI release notes:
- npm trusted publisher must be configured for package `clawhub` with repository `openclaw/clawhub`, workflow `clawhub-cli-npm-release.yml`, and environment `npm-release`.
- After a successful npm publish, the workflow creates or updates the matching GitHub Release from the `CHANGELOG.md` section and appends npm tarball/integrity proof.

If npm publish succeeds but GitHub Release creation needs repair, rerun the
GitHub Release workflow without publishing to npm again:

```bash
gh workflow run clawhub-cli-github-release.yml \
--repo openclaw/clawhub \
--ref main \
-f tag=v0.11.0 \
-f preflight_run_id=<successful preflight run id> \
-f update_existing=false
```

If the original publish workflow failed after npm publish while creating the
GitHub Release, omit `publish_run_id`; the repair workflow accepts only
successful proof run ids.

Use `update_existing=true` only when intentionally replacing the body for an
existing GitHub Release.

That workflow assumes Vercel Git integration is enabled for this repo. It does
not run `vercel deploy` directly; frontend-related steps wait for the GitHub
commit status `Vercel - clawhub` for the selected SHA, then run smoke tests
against production.
The app deploy workflow assumes Vercel Git integration is enabled for this
repo. It does not run `vercel deploy` directly; frontend-related steps wait for
the GitHub commit status `Vercel - clawhub` for the selected SHA, then run
smoke tests against production.

Ensure Convex env is set (auth + embeddings):

Expand Down
Loading