fix clawhub publish username - #36
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 48eea57dfd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - name: Publish ClawHub bundle | ||
| run: pnpm dlx clawhub@0.18.0 package publish ./packages/cli --family bundle-plugin --owner clankeroverflow | ||
| run: pnpm dlx clawhub@0.18.0 package publish ./packages/cli --family bundle-plugin --owner bernoussama |
There was a problem hiding this comment.
Use the matching ClawHub owner for the scoped package
For every CLI release, this publishes the local ./packages/cli folder whose detected package name is @clankeroverflow/cli (packages/cli/package.json:2) under bernoussama. The pinned ClawHub 0.18.0 documentation states that --owner selects the publisher and that scoped package names must match the selected owner. Because the validation dry-run at line 54 does not pass this owner, validation can succeed and the live publish will only fail after the npm staging step. Keep --owner clankeroverflow, or explicitly change the published package name if a personal publisher is intended.
Useful? React with 👍 / 👎.
No description provided.