fix(release): pass --manual-override-reason to ClawHub publish

[buremba]

What

The 9.3.0 publish run's final [4/4] Publishing to ClawHub step failed:

Manual publishes for packages with trusted publisher config require manualOverrideReason

The lobu ClawHub slug has a trusted-publisher config, so ClawHub treats the scripted clawhub package publish of @lobu/openclaw-plugin as a manual publish and requires an explicit override reason. npm published @lobu/openclaw-plugin@9.3.0 fine; only the ClawHub marketplace mirror was left behind.

Fix

Pass --manual-override-reason "synchronized npm + ClawHub release via scripts/publish-packages.mjs (publish-packages.yml)" to the publishToClawhub invocation in scripts/publish-packages.mjs.

Validation

• node --check clean.
• clawhub package publish <staged> … --manual-override-reason … --dry-run → no error, renders the full publish preview (12 files, 104.8 KB). The flag clears the rejection.

After merge, re-dispatching publish-packages.yml republishes (npm idempotently skips the already-published 9.3.0 packages) and the ClawHub step publishes lobu@9.3.0.

Summary by CodeRabbit

• Chores
  • Enhanced the package publishing process to include documented reasoning for publishes synchronized with release cycles, improving transparency and traceability of deployment operations.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 40b74591-b1be-4235-a937-9dbbc5cf0c87

📥 Commits

Reviewing files that changed from the base of the PR and between d75d07a and e04c604.

📒 Files selected for processing (1)

• scripts/publish-packages.mjs

---

📝 Walkthrough

Walkthrough

The publish-packages.mjs script now passes a --manual-override-reason flag to the clawhub package publish command when publishing to ClawHub. This flag documents that the publish is synchronized with the npm release and driven by the release workflow.

Changes

ClawHub Publish with Manual Override Reason

Layer / File(s)	Summary
Manual override reason flag addition scripts/publish-packages.mjs	The clawhub publish command now includes a --manual-override-reason flag with a documented reason string explaining that the publish is synchronized with the npm release and controlled by this script/workflow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A rabbit hops through CI with glee,
Adding notes so all can see:
"Here's why we publish, clear and true,
npm and ClawHub sync on cue!" ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the problem, fix, and validation clearly, but lacks the required test plan checklist from the template.	Add a 'Test plan' section with checkboxes for validation steps (bun run check:fix, typecheck, etc.) as required by the repository template.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: passing --manual-override-reason to ClawHub publish in the release process.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/clawhub-manual-override

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!