fix: drop requirements.txt from ClawHub payload (v3.5.1)#2
Merged
Conversation
The ClawHub package directory (wordpress-api-pro/) is published as the skill, and it otherwise ships only .json/.md/.py/.sh files. The lone requirements.txt added in 3.5.0 risked breaking ClawHub publishing, and it was optional anyway (only the ACF/SEO/JetEngine/plugin-detection scripts need `requests`). - Remove wordpress-api-pro/requirements.txt from the payload. - Install the dep directly instead: `pip install requests` (INSTALL.sh, README, SKILL.md). Core scripts stay stdlib-only. - Drop it from package.json files[]; bump to 3.5.1; CHANGELOG entry. Verified: payload now contains only .json/.md/.py/.sh; `bash -n INSTALL.sh`, package.json valid, `npm test` passes; local reinstall refreshes the Claude Code skill to v3.5.1 with no requirements.txt. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
wordpress-api-pro/is the directory published to ClawHub as the skill. It otherwise ships only.json/.md/.py/.shfiles; therequirements.txtadded in 3.5.0 was the only.txtin the payload and risked breaking ClawHub publishing. It was optional anyway — only the ACF / SEO / JetEngine / plugin-detection scripts importrequests; the core post/page/media/WooCommerce/batch scripts are stdlib-only.(The root
LICENSE.txtis unaffected — it lives outside the published skill payload.)What
wordpress-api-pro/requirements.txtfrom the payload.pip install requests— updated inINSTALL.sh,README.md,SKILL.md.package.jsonfiles[]; bump3.5.0 → 3.5.1; CHANGELOG entry.Verification
.json/.md/.py/.sh(find wordpress-api-pro -type f).bash -n INSTALL.sh,package.jsonvalid,npm testpasses (compileall + batch dry-run).requirements.txt.🤖 Generated with Claude Code