Repository navigation
Document local ClawHub releases - #12
Merged
Merged
Conversation
Pandekh
changed the title
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
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.
Document an explicit local ClawHub release process using the existing packager: sign in locally, preview an exact GitHub commit or tag, then publish it under the PandaDoc organization. Explain local CLI token storage and extend the publication wait to 30 minutes for ClawHub security checks.
GitHub pushes and merges do not publish to ClawHub. No publishing workflow or GitHub publishing secret is added. Existing client manifests, skills, hooks, MCP settings, installation paths, and plugin versions are unchanged.
Validation: the existing Claude archive payload matches main byte-for-byte; the ClawHub dry run contains the expected 19 files and 10 skills and excludes uncommitted data. Official Claude and Cursor template validators passed. Token storage and permissions were checked against the CLI implementation without reading the token value.