What are you trying to do?
Publish version 3.0.0 of the ClawHub skill pretyflaco/blink-wallet. I expected it to pass publication checks and become the latest version, as 2.6.2 did (live ~8 minutes after publishing).
Environment
- OpenClaw version: N/A (this is a ClawHub publishing problem, not a gateway problem)
- ClawHub CLI: v0.23.3, installed via npm (Node 24.22.1, nvm)
- OS: Pop!_OS 24.04 LTS
- Publish command:
clawhub skill publish blink --slug blink-wallet --owner pretyflaco --version 3.0.0 --tags latest --source-repo blinkbitcoin/blink-skills --source-ref v3.0.0 --source-commit bb1d998bf087b1e9f71d57e1c423d22ec59797f1 --source-path blink
What happened?
Publish returned pending-publication on 2026-10-25 ~09:39 UTC:
- versionId:
k97fbzf1s297hhsw9ecjnm1vx58gzwk8 - attemptId:
zx76bjbk68scewd247xcvtygh18gzdym
The listing now shows:
Publication checks failed. Version 3.0.0 is not yet public or installable. One or more security checks could not complete. The uploaded version is retained.
Secret check: passed. Security check: could not complete.
Five days later, the registry still serves 2.6.2, and clawhub inspect blink-wallet --version 3.0.0 returns Version not found.
What have I tried?
- Dry-run publish first: clean (
would-publish, 49 files). - Re-checked the registry API and
clawhub inspectseveral times over 5 days: no change. - Did not republish under a new version number, to avoid creating a duplicate pending version.
Safe diagnostics
From clawhub scan download blink-wallet --version 3.0.0:
manifest.json: statussucceeded, writtenBacktrue, last updated 2026-10-25 09:39 UTC (unchanged since)clawscan.json,endor.json,skillspector.json,virustotal.json: allnullstatic-analysis.json:suspicious.env_credential_accessandsuspicious.insecure_tls_verification. These are the same two by-design findings 2.6.2 had (the skill is an API client that readsBLINK_API_KEY;--no-verifyis opt-in and defaults to verify-on). 2.6.2 was reviewed as clean on 2026-09-16.
Ask: could you re-run the security check on the retained 3.0.0 upload? The release includes a security fix (l402-pay --no-store was silently ignored, so tokens were cached despite the opt-out), so we’d like it to reach users.